View XRT75L00D_3512452.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

exar corporation 48720 kato road, fremont ca, 94538 ? (510) 668-7000 ? fax (510) 668-7017 ? www.exar.com XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer february 2004 rev. 1.0.2 general description the XRT75L00D is a single-channel fully integrated line interface unit (liu) with sonet desynchronizer for e3/ds3/sts-1 applications. it incorporates an independent receiver, transmitter and jitter attenuator in a single 52 pin tqfp package. the XRT75L00D can be configured to operate in either e3 (34.368 mhz), ds3 (44.736 mhz) or sts-1 (51.84 mhz) modes. the transmitter can be turned off (tri-stated) for redundancy support and for conserving power. the XRT75L00Ds differential receiver provides high noise interference margin and is able to receive the data over 1000 feet of cable or with up to 12 db of cable attenuation. the XRT75L00D incorporates an advanced crystal- less jitter attenuator that can be selected either in the transmit or receive path. the jitter attenuator performance meets the etsi tbr-24 and bellcore gr-499 specifications. also, the jitter attenuator can be used for clock smoothing in sonet sts-1 to ds3 de-mapping. the XRT75L00D provides both serial microprocessor interface as well as hardware mode for programming and control. the XRT75L00D supports local, remote and digital loop-backs. the XRT75L00D also contains an on- board pseudo random binary sequence (prbs) generator and detector with the ability to insert and detect single bit error. features receiver: on chip clock and data recovery circuit for high input jitter tolerance. meets e3/ds3/sts-1 jitter tolerance requirements. detects and clears los as per g.775. meets bellcore gr-499 core jitter transfer requirements. receiver monitor mode handles up to 20 db flat loss with 6 db cable attenuation. compliant with jitter transfer template outlined in itu g.751, g.752, g.755 and gr-499-core,1995 standards. meets etsi tbr 24 jitter transfer requirements. on chip b3zs/hdb3 encoder and decoder that can be either enabled or disabled. on-chip clock synthesizer provides the appropriate rate clock from a single 12.288 mhz clock. provides low jitter output clock. transmitter: compliant with bellcore gr-499, gr-253 and ansi t1.102 specification for transmit pulse tri-state transmit output capability for redundancy applications transmitter can be turned on or off. jitter attenuator: on chip advanced crystal-less jitter attenuator. jitter attenuator can be selected in receive or transmit paths. 16, 32 or 128 bits selectable fifo size. meets the jitter and wander specifications described in t1.105.03b,etsi tbr-24, bellcore gr-253 and gr-499 standards. jitter attenuator can be disabled. de-synchronizer for sonet sts-1 to ds-3 demapping. control and diagnostics: 5 wire serial microprocessor interface for control and configuration. supports optional internal transmit driver monitoring. prbs error counter register to accumulate errors. hardware mode for control and configuration. supports local, remote and digital loop-backs. single 3.3 v 5% power supply. 5 v tolerant i/o. available in 52 pin tqfp. -40c to 85c industrial temperature range. applications e3/ds3 access equipment. dslams. digital cross connect systems. csu/dsu equipment. routers.
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 2 fiber optic terminals. transmit interface characteristics accepts either single-rail or dual-rail data from terminal equipment and generates a bipolar signal to the line integrated pulse shaping circuit. built-in b3zs/hdb3 encoder (which can be disabled). accepts transmit clock with duty cycle of 30%-70%. generates pulses that comply with the itu-t g.703 pulse template for e3 applications. generates pulses that comply with the dsx-3 pulse template, as specified in bellcore gr-499 -core and ansi t1.102_1993. generates pulses that comply with the stsx-1 pulse template, as specified in bellcore gr-253-core. transmitter can be turned off in order to support redundancy designs. receive interface characteristics integrated adaptive receive equalization for optimal clock and data recovery. declares and clears the los defect per itu-t g.775 requirements for e3 and ds3 applications. meets jitter tolerance requirements, as specified in itu-t g.823_1993 for e3 applications. meets jitter tolerance requirements, as specified in bellcore gr-499-core for ds3 applications. declares loss of signal (los) and loss of lock (lol) alarms. f igure 1. b lock d iagram of the xrt 75l00d host/hw sts-1/ds3 e3 reqen rtip rring sr/dr xrt75l03 rlb rlos jatx/rx tpdata tndata txclk taos txlev txon note: serial processor interface input pins are shared by in "host" mode and redefined in the "hardware" mode. device monitor mtip mring dmo timing control ttip tring tx pulse shaping hdb3/ b3zs encoder rlol rxon rxclkinv rxclk rpos rneg/ lcv tx control jitter attenuator mux line driver llb invert remote loopback hdb3/ b3zs decoder mux agc/ equalizer peak detector los detector slicer jitter attenuator serial processor interface local loopback clock & data recovery clock synthesizer exclk/12m reset cs sclk int sdo sdi clk_out
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 3 built-in b3zs/hdb3 decoder (which can be disabled). recovered data can be muted while the los condition is declared. outputs either single-rail or dual-rail data to the terminal equipment. jitter attenuators the XRT75L00D includes a jitter attenuator that meets the jitter requirements specified in the etsi tbr-24, bellcore gr-499 and gr-253 standards. in addition, the jitter attenuator also meets the jitter and wander specifications described in the ansi t1.105.03b 1997, bellcore gr-253 and gr-499 standards. f igure 2. p in o ut of the XRT75L00D clk_out rpos rneg (lcv) rxclk gnd refagnd rext refavdd vdd rlos rlol int (losmut) sdo (rxmon) txlev taos txavdd txon txagnd ja0 ja1 ja tx/rx sfm_en rxavdd rring rtip rxagnd XRT75L00D (top view) 40 41 42 43 44 45 46 47 48 49 50 51 52 26 25 24 23 22 21 20 19 18 17 16 15 14 1 2 3 4 5 6 7 8 9 10 11 12 13 39 38 37 36 35 34 33 32 31 30 29 28 27 dmo mtip mring jaagnd exclk/12m jaavdd txclk tpdata tndata dgnd ttip tring dvdd sclk (txclkinv) sdi (rxon) cs (rxclkinv) reqen sr/dr host/hw e3 sts1/ds3 rlb llb ict test reset
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 4 ordering information p art n umber p ackage o perating t emperature r ange XRT75L00Div 52 pin tqfp -40 c to +85 c
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 1 table of contents general description................................................................................................. 1 f eatures ............................................................................................................................... ...................... 1 a pplications ............................................................................................................................... ................ 1 t ransmit i nterface c haracteristics ....................................................................................................... 2 r eceive i nterface c haracteristics ......................................................................................................... 2 f igure 1. b lock d iagram of the xrt 75l00d.................................................................................................................... ........ 2 j itter a ttenuators ............................................................................................................................... ..... 3 f igure 2. p in o ut of the XRT75L00D ..................................................................................................................... .................... 3 ordering information ........................................................................................................... ......... 4 t able of c ontents ........................................................................................................... 1 pin descriptions (by function) ............................................................................. 4 t ransmit i nterface ............................................................................................................................... ..... 4 r eceive i nterface ............................................................................................................................... ....... 6 c lock i nterface ............................................................................................................................... .......... 8 o perating m ode s elec t ............................................................................................................................ 9 c ontrol and a larm i nterface .................................................................................................................. 9 m icroprocessor s erial interface - (host mode)......................................................................... 11 j itter a ttenuator interface .................................................................................................................. 13 a nalog p ower and g round .................................................................................................................... 14 d igital p ower and g round .................................................................................................................... 14 1.0 electrical characteristics .............................................................................................. ..... 15 t able 1: a bsolute m aximum r atings ............................................................................................................................... .......... 15 t able 2: dc e lectrical c haracteristics : .............................................................................................................................. .. 15 2.0 timing characteristics .................................................................................................. ............ 16 f igure 3. t ypical interface between terminal equipment and the XRT75L00D ( dual - rail data )........................................ 16 f igure 4. t ransmitter t erminal i nput t iming .......................................................................................................................... 16 f igure 5. r eceiver d ata output and code violation timing ................................................................................................... 17 f igure 6. t ransmit p ulse a mplitude test circuit for e3, ds3 and sts-1 r ates ................................................................. 17 3.0 line side characteristics: .............................................................................................. ......... 18 3.1 e3 line side parameters: ................................................................................................ ...................... 18 f igure 7. p ulse m ask for e3 (34.368 mbits / s ) interface as per itu - t g.703......................................................................... 18 t able 3: e3 t ransmitter and receiver line side specifications (t a = 250c and vdd = 3.3 v 5%) ................................... 18 f igure 8. b ellcore gr-253 core t ransmit o utput p ulse t emplate for sonet sts-1 a pplications ............................ 19 t able 4: sts-1 p ulse m ask e quations ............................................................................................................................... ...... 19 t able 5: sts-1 t ransmitter and r eceiver l ine s ide s pecifications (ta = 250c and vdd =3.3v 5%) ............................ 20 f igure 9. t ransmit o uput p ulse t emplate for ds3 as per b ellcore gr-499 ..................................................................... 20 t able 6: ds3 p ulse m ask e quations ............................................................................................................................... ......... 21 t able 7: ds3 t ransmitter and r eceiver l ine s ide s pecifications (t a = 250c and vdd = 3.3v 5%)................................ 21 f igure 10. m icroprocessor s erial i nterface s tructure ..................................................................................................... 22 f igure 11. t iming d iagram for the m icroprocessor s erial i nterface ................................................................................ 22 t able 8: m icroprocessor s erial i nterface t imings ( ta = 250c, vdd=3.3v 5% and load = 10 p f).................................. 23 4.0 the transmitter section: ................................................................................................ ......... 24 4.1 transmit clock: ......................................................................................................... .............................. 24 4.2 b3zs/hdb3 encoder: ...................................................................................................... .......................... 24 4.2.1 b3zs encoding: ......................................................................................................... ............................................. 24 f igure 12. s ingle -r ail or nrz d ata f ormat (e ncoder and d ecoder are e nabled )............................................................ 24 f igure 13. d ual -r ail d ata f ormat ( encoder and decoder are disabled ) ............................................................................. 24 4.2.2 hdb3 encoding:......................................................................................................... ............................................. 25 f igure 14. b3zs e ncoding f ormat ............................................................................................................................... ............ 25 f igure 15. hdb3 e ncoding f ormat ............................................................................................................................... ........... 25 4.3 transmit pulse shaper: .................................................................................................. ...................... 26 4.3.1 guidelines for using transmit build out circuit: ....................................................................... .......... 26 4.3.2 interfacing to the line:............................................................................................... ..................................... 26 4.4 transmit drive monitor: ................................................................................................. ...................... 26 4.5 transmitter section on/off: ............................................................................................. ................. 27 5.0 the receiver section: ................................................................................................... .............. 27 5.1 agc/equalizer: .......................................................................................................... ................................ 27 f igure 16. t ransmit d river m onitor set - up . ........................................................................................................................... 27
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 2 5.1.1 interference tolerance: ................................................................................................ ................................ 28 f igure 17. i nterference m argin t est s et up for ds3/sts-1................................................................................................ 28 5.2 clock and data recovery: ................................................................................................ .................. 29 5.3 b3zs/hdb3 decoder: ...................................................................................................... ........................... 29 f igure 18. i nterference m argin t est s et up for e3.............................................................................................................. 29 t able 9: i nterference m argin t est r esults ........................................................................................................................... 29 5.4 los (loss of signal) detector: .......................................................................................... ................ 30 5.4.1 ds3/sts-1 los condition: ............................................................................................... ..................................... 30 d isabling alos/dlos d etector :............................................................................................................30 5.4.2 e3 los condition:...................................................................................................... ............................................ 30 t able 10: t he alos (a nalog los) d eclaration and c learance t hresholds for a given setting of reqen (ds3 and sts-1 a pplications ) .............................................................................................................................. ................................. 30 5.4.3 muting the recovered data with los condition:.......................................................................... ......... 31 f igure 19. l oss o f s ignal d efinition for e3 as per itu-t g.775.......................................................................................... 31 f igure 20. l oss of s ignal d efinition for e3 as per itu-t g.775. ......................................................................................... 31 6.0 jitter: ................................................................................................................. ...............................32 6.1 jitter tolerance - receiver: ............................................................................................ .................. 32 6.1.1 ds3/sts-1 jitter tolerance requirements:............................................................................... ................ 32 f igure 21. j itter t olerance m easurements ............................................................................................................................ 32 6.1.2 e3 jitter tolerance requirements:...................................................................................... ....................... 33 f igure 22. i nput j itter t olerance f or ds3/sts-1 ................................................................................................................ 33 f igure 23. i nput j itter t olerance for e3 ............................................................................................................................ .. 33 6.2 jitter transfer - receiver/transmitter: ................................................................................. ..... 34 6.3 jitter generation: ...................................................................................................... ............................ 34 6.4 jitter attenuator: ...................................................................................................... ........................... 34 t able 11: j itter a mplitude versus m odulation f requency (j itter t olerance )................................................................... 34 t able 12: j itter t ransfer s pecifications ............................................................................................................................... .34 t able 13: j itter t ransfer p ass m asks ............................................................................................................................... ..... 35 f igure 24. j itter t ransfer r equirements and j itter a ttenuator p erformance ................................................................ 35 7.0 serial host interface: .................................................................................................. .............36 t able 14: f unctions of shared pins ............................................................................................................................... .......... 36 t able 15: r egister m ap and b it n ames ............................................................................................................................... ..... 36 t able 16: r egister m ap d escription ............................................................................................................................... ......... 37 t able 17: r egister m ap d escription - g lobal ......................................................................................................................... 41 8.0 diagnostic features: .................................................................................................... ..............42 8.1 prbs generator and detector: ............................................................................................ ............ 42 8.2 loopbacks: .............................................................................................................. ................................... 43 f igure 25. prbs mode ................................................................................................................ ............................................. 43 8.2.1 analog loopback:....................................................................................................... ........................................ 44 8.2.2 digital loopback:...................................................................................................... .......................................... 44 f igure 26. a nalog l oopback ............................................................................................................................... ...................... 44 8.2.3 remote loopback:....................................................................................................... ........................................ 45 8.3 transmit all ones (taos): ............................................................................................... ..................... 45 f igure 27. d igital l oopback ............................................................................................................................... ....................... 45 f igure 28. r emote l oopback ............................................................................................................................... ..................... 45 f igure 29. t ransmit a ll o nes (taos) ........................................................................................................................ .............. 46 9.0 the sonet/sdh de-sync function within the liu ...............................................................47 9.1 background and detailed information - sonet de-sync applications ............................ 47 f igure 30. a s imple i llustration of a ds3 signal being mapped into and transported over the sonet n etwork ........ 48 9.2 mapping/de-mapping jitter/wander ........................................................................................ ......... 49 9.2.1 how ds3 data is mapped into sonet ...................................................................................... ....................... 49 9.2.1.1 a b rief d escription of an sts-1 f rame ......................................................................................................... 49 f igure 31. a s imple i llustration of the sonet sts-1 f rame .............................................................................................. 50 f igure 32. a s imple i llustration of the sts-1 f rame s tructure with the toh and the e nvelope c apacity b ytes d esignated 51 f igure 33. t he b yte -f ormat of the toh within an sts-1 f rame .......................................................................................... 52 f igure 34. t he b yte -f ormat of the toh within an sts-1 f rame .......................................................................................... 53 9.2.1.2 m apping ds3 data into an sts-1 spe ............................................................................................................ 54 f igure 35. i llustration of the b yte s tructure of the sts-1 spe....................................................................................... 54 f igure 36. a n i llustration of t elcordia gr-253-core' s r ecommendation on how map ds3 data into an sts-1 spe... 55 f igure 37. a s implified "b it -o riented " v ersion of t elcordia gr-253-core' s r ecommendation on how to map ds3 data into an sts-1 spe ..................................................................................................................... ......................................... 55 9.2.2 ds3 frequency offsets and the use of the "stuff opportunity" bits ......................................... 56 9.2.2.1 t he i deal c ase for m apping ds3 data into an sts-1 s ignal ( e . g ., with no f requency o ffsets ) ............ 57
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 3 f igure 38. a s imple i llustration of a ds3 d ata -s tream being m apped into an sts-1 spe, via a pte .............................. 57 9.2.2.2 t he 44.736m bps + 1 ppm c ase ........................................................................................................................... 58 f igure 39. a n i llustration of the sts-1 spe traffic that will be generated by the "s ource " pte, when mapping in a ds3 signal that has a bit rate of 44.736m bps + 1 ppm , into an sts-1 signal ................................................................ 58 9.2.2.3 t he 44.736m bps - 1 ppm c ase ............................................................................................................................ 59 9.3 jitter/wander due to pointer adjustments .............................................................................. 60 9.3.1 the concept of an sts-1 spe pointer.................................................................................... ....................... 60 f igure 40. a n i llustration of the sts-1 spe traffic that will be generated by the s ource pte, when mapping a ds3 signal that has a bit rate of 44.736m bps - 1 ppm , into an sts-1 signal ............................................................................ 60 f igure 41. a n i llustration of an sts-1 spe straddling across two consecutive sts-1 frames .................................... 61 9.3.2 pointer adjustments within the sonet network ........................................................................... ....... 62 f igure 42. t he b it - format of the 16-b it w ord ( consisting of the h1 and h2 bytes ) with the 10 bits , reflecting the location of the j1 byte , designated ............................................................................................................................... .......... 62 f igure 43. t he r elationship between the c ontents of the "p ointer b its " ( e . g ., the 10- bit expression within the h1 and h2 bytes ) and the l ocation of the j1 b yte within the e nvelope c apacity of an sts-1 f rame ................................ 62 9.3.3 causes of pointer adjustments .......................................................................................... ......................... 63 f igure 44. a n i llustration of an sts-1 signal being processed via a s lip b uffer ............................................................. 64 f igure 45. a n i llustration of the b it f ormat within the 16- bit word ( consisting of the h1 and h2 bytes ) with the "i" bits designated ............................................................................................................................... .................................... 65 f igure 46. a n i llustration of the b it -f ormat within the 16- bit word ( consisting of the h1 and h2 bytes ) with the "d" bits designated ............................................................................................................................... .................................... 66 9.3.4 why are we talking about pointer adjustments? .......................................................................... ..... 67 9.4 clock gapping jitter .................................................................................................... ......................... 67 f igure 47. i llustration of the t ypical a pplications for the liu in a sonet d e -s ync a pplication .................................. 67 9.5 a review of the category i intrinsic jitter requirements (per telcordia gr-253-core) for ds3 applications .......................................................................................................... .................. 68 t able 18: s ummary of "c ategory i i ntrinsic j itter r equirement per t elcordia gr-253-core, for ds3 applications .. 68 9.5.1 ds3 de-mapping jitter.................................................................................................. ....................................... 69 9.5.2 single pointer adjustment .............................................................................................. ............................... 69 9.5.3 pointer burst.......................................................................................................... .............................................. 69 f igure 48. i llustration of s ingle p ointer a djustment s cenario ......................................................................................... 69 9.5.4 phase transients....................................................................................................... .......................................... 70 f igure 49. i llustration of b urst of p ointer a djustment s cenario ..................................................................................... 70 f igure 50. i llustration of "p hase -t ransient " p ointer a djustment s cenario ..................................................................... 70 9.5.5 87-3 pattern........................................................................................................... ................................................. 71 9.5.6 87-3 add ............................................................................................................... ...................................................... 71 f igure 51. a n i llustration of the 87-3 c ontinuous p ointer a djustment p attern ............................................................. 71 9.5.7 87-3 cancel............................................................................................................ .................................................. 72 f igure 52. i llustration of the 87-3 a dd p ointer a djustment p attern ................................................................................ 72 f igure 53. i llustration of 87-3 c ancel p ointer a djustment s cenario ................................................................................ 72 9.5.8 continuous pattern..................................................................................................... ...................................... 73 9.5.9 continuous add ........................................................................................................ ........................................... 73 f igure 54. i llustration of c ontinuous p eriodic p ointer a djustment s cenario ................................................................ 73 9.5.10 continuous cancel..................................................................................................... ...................................... 74 f igure 55. i llustration of c ontinuous -a dd p ointer a djustment s cenario ........................................................................ 74 f igure 56. i llustration of c ontinuous -c ancel p ointer a djustment s cenario ................................................................... 74 9.6 a review of the ds3 wander requirements per ansi t1.105.03b-1997. ................................. 75 9.7 a review of the intrinsic jitter and wander capabilities of the liu in a typical system application ................................................................................................................... ............................ 75 9.7.1 intrinsic jitter test results.......................................................................................... ................................ 75 t able 19: s ummary of "c ategory i i ntrinsic j itter t est r esults " for sonet/ds3 a pplications ..................................... 75 9.7.2 wander measurement test results........................................................................................ .................... 76 9.8 designing with the liu .................................................................................................. ......................... 76 9.8.1 how to design and configure the liu to permit a system to meet the above-mentioned intrin- sic jitter and wander requirements ............................................................................................. ............... 76 f igure 57. i llustration of the liu being connected to a m apper ic for sonet d e -s ync a pplications .......................... 76 c hannel c ontrol r egister ..................................................................................................................... 77 c hannel c ontrol r egister ..................................................................................................................... 78 j itter a ttenuator c ontrol r egister .................................................................................................... 78 9.8.2 recommendations on pre-processing the gapped clocks (from the mapper/asic device) prior to routing this ds3 clock and data-signals to the transmit inputs of the liu ........................ 79 9.8.2.1 some notes prior to starting this discussion: ......................................................................... ... 79 j itter a ttenuator c ontrol r egister .................................................................................................... 79 j itter a ttenuator c ontrol r egister .................................................................................................... 79 9.8.2.2 our pre-processing recommendations .................................................................................... ........ 80
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 4 f igure 58. i llustration of minor pattern p1.............................................................................................................. ....... 80 f igure 59. i llustration of minor pattern p2.............................................................................................................. ....... 81 f igure 60. i llustration of p rocedure which is used to s ynthesize major pattern a .................................................. 81 f igure 61. i llustration of minor pattern p3.............................................................................................................. ....... 82 f igure 62. i llustration of p rocedure which is used to s ynthesize pattern b............................................................... 82 9.8.3 how does the liu permit the user to comply with the sonet aps recovery time requirements of 50ms (per telcordia gr-253-core)? ........................................................................................... ................. 83 f igure 63. i llustration of the super pattern which is output via the "oc-n to ds3" m apper ic ............................... 83 f igure 64. s imple i llustration of the liu being used in a sonet d e -s ynchronizer " a pplication .................................... 83 t able 20: m easured aps r ecovery t ime as a function of ds3 ppm offset ......................................................................... 84 j itter a ttenuator c ontrol r egister ....................................................................................................84 9.8.4 how should one configure the liu, if one needs to support "daisy-chain" testing at the end customer's site? ............................................................................................................... ...................................... 85 j itter a ttenuator c ontrol r egister ....................................................................................................85 o rdering i nformation ..............................................................................................................................8 6 package dimensions.................................................................................................86 revision history ............................................................................................................... ...............87
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 4 pin descriptions ( by function ) transmit interface p in #s ignal n ame t ype d escription 4txon i transmitter on input setting this input pin "high" turns on the transmitter. n otes : 1. even when the XRT75L00D is configured in host mode, this pin still controls the ttip and tring outputs 2. when the transmitter is turned off either in host or hardware mode,the ttip and tring outputs are tri-stated. 3. this pin is internally pulled down 46 txclk i transmit clock input for tpdata and tndata the frequency accuracy of this input clock must be of nominal bit rate 20 ppm. the duty cycle can be 30%-70%. the XRT75L00D samples the tpdata and tndata pins on the falling or rising edge of txclk signal based on the status of txclkinv pin (in hardware mode) or the status of the bit in the channel register (in host mode). 26 txclkinv/ sclk i transmit clock invert or serial clock input: function of this depends on whether the XRT75L00D is configured to operate in hardware mode or host mode. in hardware mode, setting this input pin high configures the transmitter to sample the tpdata and tndata data on the rising edge of the txclk. n ote : if the XRT75L00D is configured in host mode, this pin functions as sclk input pin (please refer to the pin description for microprocessor interface). 48 tndata i transmit negative data input if the XRT75L00D is configured in dual-rail mode, this pin is sampled on the falling or rising edge of txclk based on the status of the tclkinv pin (in hard- ware mode) or the status of the control bit in the channel register (in host mode). n otes : 1. this input pin is ignored and should be tied to gnd if the transmitter section is configured to accept single-rail data from the terminal equipment. 47 tpdata i transmit positive data input the XRT75L00D samples this pin on the falling or rising edge of txclk based on the status of the tclkinv pin (in hardware mode) or the status of the control bit in the channel register (in host mode). 50 ttip o transmit ttip output the XRT75L00D uses this pin along with tring to transmit a bipolar signal to the line using a 1:1 transformer.
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 5 51 tring o transmit ring output the XRT75L00D uses this pin along with ttip to transmit a bipolar signal to the line using a 1:1 transformer. 1txlev i transmit line build-out enable/disable select this input pin is used to enable or disable the transmit line build-out circuit. setting this pin to "high" disables the line build-out circuit. in this mode, par- tially-shaped pulses are output onto the line via the ttip and tring output pins. setting this pin to "low" enables the line build-out circuit. in this mode, shaped pulses are output onto the line via the ttipand tring output pins. to comply with the isolated dsx-3/stsx-1 pulse template requirements per bellcore gr-499-core or bellcore gr-253-core: 1. set this pin to "1" if the cable length between the cross-connect and the transmit output is greater than 225 feet. 2. set this pin to "0" if the cable length between the cross-connect and the transmit output is less than 225 feet. this pin is active only if the following two conditions are true: a. the XRT75L00D is configured to operate in either the ds3 or sonet sts-1 modes. b. the XRT75L00D is configured to operate in the hardware mode. n otes : 1. this pin is internally pulled down. 2. if the XRT75L00D is configured in host mode, this pin may be tied to gnd. transmit interface p in #s ignal n ame t ype d escription
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 6 receive interface p in #s ignal n ame t ype d escription 25 rxon/ sdi i receiver turn on input or serial data input: function of this pin depends on whether the XRT75L00D is configured to oper- ate in hardware mode or host mode. in hardware mode, setting this input pin high turns on and enables the receiver.. n otes : 1. if the XRT75L00D is configured in host mode, this pin functions as sdi input pin (please refer to the pin description for microprocessor interface) 2. this pin is internally pulled down. 23 reqen i receive equalization enable input setting this input pin "high" enables the internal receive equalizer. setting this pin "low" disables the internal receive equalizer. n otes : 1. this input pin is ignored and may be connected to gnd if the XRT75L00D is operating in the host mode 2. this pin is internally pulled down. 36 rxclk o receive clock output the recovered clock signal from the incoming line signal is output through this pin.by default, the receiver section outputs data via rpos and rneg pins on the rising edge of this clock signal. configure the receiver section to update data on the rpos and rneg pins on the falling edge of rxclk by doing the following: a) operating in hardware mode , pull the rxclkinv pin to high. b) operating in host mode , write a 1 to rxclkinv bit field within the receive control register. 24 rxclkinv/ cs i rxclk invert or chip select : function of this pin depends on whether the XRT75L00D is configured to oper- ate in hardware mode or host mode. in hardware mode, setting this input pin high configures the receiver sec- tion to invert the rxclk output signals and outputs the recovered data via rpos and rneg on the falling edge of rxclk. n ote : if the XRT75L00D is configured in host mode, this pin functions as cs input pin (please refer to the pin description for microprocessor interface). 38 rpos o receive positive data output this output pin pulses high" whenever the XRT75L00D has received a posi- tive polarity pulse in the incoming line signal at the rtip/rring inputs.
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 7 37 rneg/lcv o receive negative data output/line code violation indicator function of these pins depends on whether the XRT75L00D is configured in single rail or dual rail mode. if the XRT75L00D is configured in dual rail mode, a negative pulse is output through rneg. in hardware mode: tie the pin sr/dr (pin 22) high to configure the XRT75L00D in single rail mode and tie low to configure in dual rail mode. in host mode: XRT75L00D can be configured in single rail or dual rail by setting or clearing the bit in the block control register. line code violation indicator if the XRT75L00D is configured in single rail mode then: whenever the receiver section detects a line code violation, it pulses this output pin high. this output pin remains low at all other times. it is advisable to sample this output pin using the rxclk output signal. 11 rring i receive ring input this input pin along with rtip is used to receive the bipolar line signal from the remote ds3/e3/sts-1 terminal. 12 rtip i receive tip input this input pin along with rrng is used to receive the bipolar line signal from the remote ds3/e3/sts-1 terminal. 27 rxmon/ sdo i receive monitoring mode or serial data output: in hardware mode, when this pin is tied high XRT75L00D configures into monitoring channel. in the monitoring mode, the receiver is capable of monitor- ing the signals with 20 db flat loss plus 6 db cable attenuation. this allows to monitor very weak signal before declaring los. in host mode, XRT75L00D can be configured to be a monitoring channel by setting the bits in the receive control register. n ote : if the XRT75L00D is configured in host mode, this pin functions as sdo pin (please refer to the pin description for the microprocessor interface). receive interface p in #s ignal n ame t ype d escription
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 8 clock interface p in #s ignal n ame t ype d escription 44 exclk/12m i clock input (34.368 mhz or 44.736 mhz or 51.84 mhz 20 ppm): based on the mode selected, provide the appropriate reference clock signal. if the XRT75L00D is configured for single frequency mode with the sfm_en tied high, then provide a 12.288 mhz 20 ppm clock and depending on the mode, the correct frequency is generated internally by the clock synthesizer.. 9sfm_en i single frequency enable: tie this pin high to select the single frequency mode. when enabled, a single frequency clock, 12.288 mhz is input through the exclk input pin and the inter- nal clock synthesizer generates the appropriate clock frequency. n ote : this pin is internally pulled down. 39 clk_out o clock out put: when the single frequency mode is selected, a low jitter clock will be out put. the frequency of this clock depends on whether the XRT75L00D is configured in e3 or ds3 or sts-1 mode.
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 9 operating mode select p in #s ignal n ame t ype d escription 21 host/(hw )i host/hardware mode select: tie this pin high to configure the XRT75L00D in host mode. tie this low to configure in hardware mode. when the XRT75L00D is configured in host mode, the states of many discrete input pins are ignored. n ote : this pin is internally pulled up. 20 e3 i e3 mode select input a "high" on this pin configures to operate in the e3 mode. a "low" on this pin configures to operate in either sts-1 or ds3 mode depend- ing on the setting on pin 19. n otes : 1. this pin is internally pulled down 2. this pin is ignored and may be tied to gnd if the XRT75L00D is configured to operate in host mode. 19 sts-1/ds3 i sts-1/ds3 select input a high on this pin configures to operate in sts-1 mode. a low on this pin configures to operate in ds3 mode. this pin is ignored if the e3 pin is set to high. n otes : 1. this pin is internally pulled down 2. this pin is ignored and may be tied to gnd if the XRT75L00D is configured to operate in host mode. 22 sr/dr i single-rail/dual-rail select: setting this high configures both the transmitter and receiver to operate in single-rail mode and also enables the b3zs/hdb3 encoder and decoder. in single-rail mode, transmit input at tndata should be grounded. setting this low configures both the transmitter and receiver to operate in dual-rail mode and disables the b3zs/hdb3 encoder and decoder. n ote : this pin is internally pulled down. control and alarm interface 42 mring i monitor ring input the bipolar line output signal from tring is connected to this pin via a 270 w resistor to check for line driver failure. n ote : this pin is internally pulled down. 41 mtip i monitor tip input the bipolar line output signal from ttip is connected to this pin via a 270-ohm resistor to check for line driver failure. n ote : this pin is internally pulled down. 40 dmo o drive monitor output if mtip and mring has no transition pulse for 128 32 txclk cycles, dmo goes high to indictae the driver failure. dmo output stays high until the next ami signal is detected.
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 10 30 rlos o receive loss of signal output indicator this output pin toggles "high" if receiver has detected a loss of signal condi- tion in the incoming line signal. the criteria for declaring/clearing an los condition depends upon whether it is operating in the e3 or sts-1/ds3 mode and is described in section 2.04. 29 rlol o receive loss of lock output indicator: this output pin toggles "high" if the XRT75L00D has detected a loss of lock condition. lol (loss of lock) condition is declared if the recovered clock fre- quency deviates from the reference clock frequency (available at exclk input pin) by more than 0.5%. 33 rext **** external bias control resistor of 3.3 k w 1%. should be connected to refagnd via 3.3 k w resistor. 15 test i test mode: connect this pin high to configure the XRT75L00D in test mode. n ote : this pin is internally pulled down. 16 ict i in-circuit test input : setting this pin "low" causes all digital and analog outputs to go into a high- impedance state to allow for in-circuit testing. for normal operation, set this pin "high". n ote : this pin is internally pulled high". 2taos i transmit all ones select a high" on this pin causes the transmitter section to generate and transmit a continuous ami all 1s pattern onto the line. the frequency of this 1s pattern is determined by txclk. n otes : 1. this input pin is ignored if the XRT75L00D is operating in the host mode and should be tied to gnd. 2. analog loopback and remote loopback have priority over request. 3. this pin is internally pulled down. 28 losmut/ int i/o mute-upon-los enable input or interrupt ouput: in hardware mode, setting this pin high configures the XRT75L00D to mute the recovered data on the rpos and rneg whenever an los condition is declared. rpos and rneg outputs are pulled low. n ote : if the XRT75L00D is configured in host mode, this pin functions as int pin (please refer to the pin description for the microprocessor interface). control and alarm interface
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 11 17 llb i local loop-back this input pin along with rlb configures different loop-back modes. n ote : this input pin is ignored and may be connected to gnd if the XRT75L00D is operating in the host mode. 18 rlb i remote loop-back this input pin along with llb configures different loop-back modes. n ote : this input pin is ignored and should be connected to gnd if the XRT75L00D is operating in the host mode. microprocessor serial interface - (host mode) p in #s ignal n ame t ype d escription 24 cs /rxclkinv i microprocessor serial interface - chip select tie this low to enable the communication with serial microprocessor inter- face. n ote : if the XRT75L00D is configured in hardware mode,this pin functions as rxclkinv. 26 sclk/txclkinv i serial interface clock input the data on the sdi pin is sampled on the rising edge of this signal. addition- ally, during read operations the microprocessor serial interface updates the sdo output on the falling edge of this signal. n ote : if the XRT75L00D is configured in hardware mode, this pin functions as txclkinv. 25 sdi/rxon i serial data input: data is serially input through this pin. the input data is sampled on the rising edge of the sclk pin (pin 26). n otes : 1. this pin is internally pulled down 2. if the XRT75L00D is configured in hardware mode, this pin functions as rxon. 27 sdo/rxmon o serial data output: this pin serially outputs the contents of the specified command register during read operations. the data is updated on the falling edge of the sclk and this pin is tri-stated upon completion of data transfer. n ote : if the XRT75L00D is configured in hardware mode, this pin functions as rxmon. control and alarm interface rlb 0 0 loopback mode normal operation analog local llb 0 1 1 1 remote digital 0 1
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 12 14 reset i register reset: setting this input pin "low" causes the XRT75L00D to reset the contents of the command registers to their default settings and default operating configuration n ote : this pin is internally pulled up. 28 int/ losmut i/o interrupt output: this pin functions as interrupt output for serial interface. a transition to low indicates that an interrupt has been generated by the serial interface. the inter- rupt function can be disabled by setting the interrupt enable bit to 0 in the channel control register. n ote : if the XRT75L00D is in hardware mode, this pin functions as losmut. microprocessor serial interface - (host mode) p in #s ignal n ame t ype d escription
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 13 jitter attenuator interface p in #s ignal n ame t ype d escription 6 ja0 i disable jitter attenuator/fifo size select:: in hardware mode, this pin along with ja1 pin provides the following functions in the table below. n ote : this pin is internally pulled down. 7 ja1 i disable jitter attenuator/fifo size select: in hardware mode, this pin along with ja0 pin provides the functions in the table above. n ote : this pin is internally pulled down. 8 ja tx/rx i jitter attenuator select: in hardware mode setting this pin high selects the jitter attenuator in the transmit path and setting low selects in receive path. n ote : this pin is internally pulled down. ja0 0 0 operation 16 bit fifo 32 bit fifo ja1 0 1 1 1 128 bit fifo disable jitter attenuator 0 1
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 14 analog power and ground p in #s ignal n ame t ype d escription 3 txavdd **** transmitter analog vdd 3.3 v 5% 10 rxavdd **** receiver analog vdd 3.3 v 5% 32 refavdd **** reference analog vdd 3.3 v 5% 5 txagnd **** transmitter analog gnd 13 rxagnd **** receiver analog gnd 34 refagnd **** reference analog gnd 45 jaavdd **** jitter attenuator analog vdd 3.3 v 5% 43 jaagnd **** jitter attenuator analog gnd digital power and ground p in #s ignal n ame t ype d escription 31 dvdd **** vdd 3.3 v 5% receiver digital 35 dgnd **** gnd 52 dvdd **** vdd 3.3 v 5% transmitter digital 49 dgnd **** gnd
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 15 1.0 electrical characteristics n otes : 1. exposure to or operating near the min or max values for extended period may cause permanent failure and impair reliability of the device. 2. esd testing method is per mil-std-883d,m-3015.7 n otes : 1. not applicable for pins with pull-up or pull-down resistors. 2. the digital inputs and outputs are ttl 5v compliant. t able 1: a bsolute m aximum r atings symbol p arameter min max units comments v dd supply voltage -0.5 6.0 v note 1 v in input voltage at any pin -0.5 5+0.5 v note 1 i in input current at any pin 100 ma note 1 s temp storage temperature -65 150 0 c note 1 a temp ambient operating temperature -40 85 0 c linear airflow 0 ft./min thetaja thermal resistance 20 0 c/w linear air flow 0ft/min thetajc 6 0 c/w m levl exposure to moisture 5 level eia/jedec jesd22-a112-a esd esd rating 2000 v note 2 t able 2: dc e lectrical c haracteristics : symbol p arameter min . typ . max . units dv dd digital supply voltage 3.135 3.3 3.465 v av dd analog supply voltage 3.135 3.3 3.465 v i cc supply current (measured while transmitting and receiving all 1s) 75 150 225 ma p dd power dissipation 235 495 780 mw v il input low voltage 0.8 v v ih input high voltage 2.0 5.0 v v ol output low voltage, i out = - 4ma 0.4 v v oh output high voltage, i out = 4 ma 2.4 v i l input leakage current 1 10 m a c i input capacitance 10 pf c l load capacitance 10 pf
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 16 2.0 timing characteristics f igure 3. t ypical interface between terminal equipment and the XRT75L00D ( dual - rail data ) f igure 4. t ransmitter t erminal i nput t iming symbol parameter min typ max units txclk duty cycle e3 ds3 sts-1 30 50 34.368 44.736 51.84 70 % mhz mhz mhz t rtx txclk rise time (10% to 90%) 4 ns t ftx txclk fall time (10% to 90%) 4 ns t tsu tpdata/tndata to txclk falling set up time 3 ns t tho tpdata/tndata to txclk falling hold time 3 ns t tdy ttip/tring to txclk rising propagation delay time 8 ns terminal equipment (e3/ds3 or sts-1 framer) exar e3/ds3/sts-1 liu transmit logic block txpos txneg txlineclk tpdata tndata txclk tpdata or tndata ttip or tring txclk t tsu t tho t rtx t ftx t tdy
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 17 f igure 5. r eceiver d ata output and code violation timing symbol parameter min typ max units rxclk duty cycle e3 ds3 sts-1 45 50 34.368 44.736 51.84 55 % mhz mhz mhz t rrx rxclk rise time (10% o 90%) 2 4 ns t frx rxclk falling time (10% to 90%) 2 4 ns t co rxclk to rpos/rneg delay time 4 ns t lcvo rxclk to rising edge of lcv output delay 2.5 ns f igure 6. t ransmit p ulse a mplitude test circuit for e3, ds3 and sts-1 r ates rclk t rrx t frx rpos or rneg lcv t lcvo t co 3.3k w + 1% ttip tring 1:1 r3 75 w txpos txneg txlineclk tpdata tndata txclk rext 37.4 w + 1% 37.4 w +1% r1 r2 refagnd
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 18 3.0 line side characteristics: 3.1 e3 line side parameters: the XRT75L00D meets the pulse shape specified in itu-t g.703 for 34.368 mbits/s operation at the secondary of the transformer. the pulse mask as specified in itu-t g.703 for 34.368 mbits/s is shown in figure 7. f igure 7. p ulse m ask for e3 (34.368 mbits / s ) interface as per itu - t g.703 t able 3: e3 t ransmitter and receiver line side specifications (t a = 25 0 c and vdd = 3.3 v 5%) parameter min typ max units t ransmitter line side output characteristics transmit output pulse amplitude (measured at secondary of the transformer) 0.90 1.00 1.10 v pk transmit output pulse amplitude ratio 0.95 1.00 1.05 transmit output pulse width 12.5 14.55 16.5 ns intrinsic jitter 0.02 0.05 ui pp r eceiver line side input characteristics receiver sensitivity (length of cable) 1200 feet interference margin -20 -15 db jitter tolerance @ jitter frequency 800khz 0.15 0.28 ui pp signal level to declare loss of signal -35 db signal level to clear loss of signal -15 db occurence of los to los declaration time 10 255 ui termination of los to los clearance time 10 255 ui 0% 50% v = 100% 14.55ns nominal pulse 12.1ns (14.55 - 2.45) 17 ns (14.55 + 2.45) 8.65 ns 10% 10% 20%
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 19 f igure 8. b ellcore gr-253 core t ransmit o utput p ulse t emplate for sonet sts-1 a pplications t able 4: sts-1 p ulse m ask e quations t ime in u nit i ntervals n ormalized a mplitude lower curve -0.85 < t < -0.38 - 0.03 -0.38 < t < 0.36 0.36 < t < 1.4 - 0.03 upper curve -0.85 < t < -0.68 0.03 -0.68 < t < 0.26 0.26 < t < 1.4 0.1 + 0.61 x e -2.4[t-0.26] sts-1 pulse template -0.2 0 0.2 0.4 0.6 0.8 1 1.2 -1 -0.9 -0.8 - 0. 7 -0.6 - 0.5 - 0. 4 - 0.3 - 0.2 -0.1 0 0.1 0. 2 0.3 0. 4 0.5 0. 6 0. 7 0.8 0. 9 1 1.1 1. 2 1.3 1. 4 time, in ui normalized amplitude lower curve upper curve 0.5 1 p 2 -- -1 t 0.18 ---------- ? ? 0.03 C + ? sin + 0.5 1 p 2 -- - 1 t 0.34 ---------- ? ? 0.03 ++ ? sin +
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 20 t able 5: sts-1 t ransmitter and r eceiver l ine s ide s pecifications (ta = 25 0 c and vdd =3.3v 5%) p arameter m in t yp m ax u nits t ransmitter line side output characteristics transmit output pulse amplitude (measured with txlev = 0) 0.65 0.75 0.90 v pk transmit output pulse amplitude (measured with txlev = 1) 0.90 1.00 1.10 v pk transmit output pulse width 8.6 9.65 10.6 ns transmit output pulse amplitude ratio 0.90 1.00 1.10 intrinsic jitter 0.02 0.05 ui pp r eceiver line side input characteristics receiver sensitivity (length of cable) 900 1100 feet jitter tolerance @ jitter frequency 400 khz 0.15 0.60 ui pp signal level to declare loss of signal refer to table 10 signal level to clear loss of signal refer to table 10 f igure 9. t ransmit o uput p ulse t emplate for ds3 as per b ellcore gr-499 ds3 pulse template -0.2 0 0.2 0.4 0.6 0.8 1 1.2 -1 - 0.9 - 0 .8 - 0.7 - 0.6 - 0.5 - 0.4 - 0. 3 - 0.2 - 0 .1 0 0. 1 0 . 2 0. 3 0.4 0. 5 0 . 6 0. 7 0 . 8 0. 9 1 1.1 1 . 2 1 . 3 1 . 4 time, in ui normalized amplitude lower curve upper curve
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 21 t able 6: ds3 p ulse m ask e quations t ime in u nit i ntervals n ormalized a mplitude lower curve -0.85 < t < -0.36 - 0.03 -0.36 < t < 0.36 0.36 < t < 1.4 - 0.03 upper curve -0.85 < t < -0.68 0.03 -0.68 < t < 0.36 0.36 < t < 1.4 0.08 + 0.407 x e -1.84[t-0.36] t able 7: ds3 t ransmitter and r eceiver l ine s ide s pecifications (t a = 25 0 c and vdd = 3.3v 5%) p arameter m in t yp m ax u nits t ransmitter line side output characteristics transmit output pulse amplitude (measured with txlev = 0) 0.65 0.75 0.85 v pk transmit output pulse amplitude (measured with txlev = 1) 0.90 1.00 1.10 v pk transmit output pulse width 10.10 11.18 12.28 ns transmit output pulse amplitude ratio 0.90 1.00 1.10 intrinsic jitter 0.02 0.05 ui pp r eceiver line side input characteristics receiver sensitivity (length of cable) 900 1100 feet jitter tolerance @ 400 khz (cat ii) 0.15 0.60 ui pp signal level to declare loss of signal refer to table 10 signal level to clear loss of signal refer to table 10 0.5 1 p 2 -- -1 t 0.18 ---------- ? ? 0.03 C + ? sin + 0.5 1 p 2 -- - 1 t 0.34 ---------- ? ? 0.03 ++ ? sin +
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 22 f igure 10. m icroprocessor s erial i nterface s tructure f igure 11. t iming d iagram for the m icroprocessor s erial i nterface d0 d1 d2 d7 d6 d5 d4 d3 high z sdo a0 d0 r/w d1 0 a5 a4 a3 a2 a1 d7 d6 d5 d4 d3 d2 sdi 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 sclk cs high z sdi r/w a1 a0 cs sclk cs sclk sdi sdo d0 d1 d2 d7 t 21 t 22 t 23 t 24 t 26 t 27 t 28 t 29 t 30 t 31 t 32 hi-z hi-z t 25
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 23 t able 8: m icroprocessor s erial i nterface t imings ( t a = 25 0 c, v dd =3.3v 5% and load = 10 p f) s ymbol p arameter m in .t yp .m ax u nits t 21 cs low to rising edge of sclk 5 ns t 22 sdi to rising edge of sclk 5 ns t 23 sdi to rising edge of sclk hold time 5 ns t 24 sclk "low" time 25 ns t 25 sclk "high" time 25 ns t 26 sclk period 50 ns t 27 falling edge of sclk to rising edge of cs 0ns t 28 cs "inactive" time 50 ns t 29 falling edge of sclk to sdo valid time 20 ns t 30 falling edge of sclk to sdo invalid time 10 ns t 31 rising edge of cs to high z 10 ns t 32 rise/fall time of sdo output 5 ns
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 24 4.0 the transmitter section: the transmitter section accepts ttl/cmos level signals from the terminal equipment in the selectable data formats. in single-rail or un-encoded non-return-to-zero (nrz) input data via tpdata pin while the tndata pin must be grounded. the nrz or single-rail mode is selected when the sr/dr input pin is high (in hardware mode) or bit 0 of the control register is 1 (in host mode). figure 12 illustrates the single-rail or nrz format. in dual-rail mode, data is input via tpdata and tndata pins. tpdata contains positive data and tndata contains negative data. the sr/dr input pin = low (in hardware mode) or bit 0 of the control register = 0 (in host mode) enables the dual-rail mode. figure 13 illustrates the dual-rail data format. convert the cmos level b3zs or hdb3 encoded data into pulses with shapes that are compliant with the various industry standard pulse template requirements. figure 7, figure 8 and figure 9 illustrate the pulse template requirements. encode the un-encoded nrz data into either b3zs format (for ds3 or sts-1) or hdb3 format (for e3) and convert to pulses with shapes and width that are compliant with industry standard pulse template requirements. figure 7,figure 8 and figure 9 illustrate the pulse template requirements. 4.1 t ransmit c lock : the transmit clock applied via txclk pin, for the selected data rate (for e3 = 34.368 mhz, ds3 = 44.736 mhz or sts-1 = 51.84 mhz), is duty cycle corrected by the internal pll circuit to provide a 50% duty cycle clock to the pulse shaping circuit. this allows a 30% to 70% duty cycle transmit clock be supplied and thus eliminates the need to use an expensive oscillator. 4.2 b3zs/hdb3 e ncoder : when the single-rail (nrz) data format is selected, the encoder block encodes the data into either b3zs format (for either ds3 or sts-1) or hdb3 format (for e3). 4.2.1 b3zs encoding: f igure 12. s ingle -r ail or nrz d ata f ormat (e ncoder and d ecoder are e nabled ) f igure 13. d ual -r ail d ata f ormat ( encoder and decoder are disabled ) txclk tpdata data 1 1 0 txclk tpdata tndata data 1 1 0
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 25 an example of b3zs encoding is shown in figure 14. if the encoder detects an occurrence of three consecutive zeros in the data stream, it is replaced with either b0v or 00v, where b refers to bipolar pulse that is compliant with the alternating polarity requirement of the ami (alternate mark inversion) line code and v refers to a bipolar violation (e.g., a bipolar pulse that violates the ami line code). the substitution of b0v or 00v is made so that an odd number of bipolar pulses exist between any two consecutive violation (v) pulses. this avoids the introduction of dc component into the line signal. 4.2.2 hdb3 encoding: an example of the hdb3 encoding is shown in figure 15.if the hdb3 encoder detects an occurrence of four consecutive zeros in the data stream, then the four zeros are substituted with either 000v or b00v pattern. the substitution code is made in such a way that an odd number of bipolar (b) pulses exist between any consecutive v pulses. this avoids the introduction of dc component into the analog signal. f igure 14. b3zs e ncoding f ormat f igure 15. hdb3 e ncoding f ormat 000 1 1 1 1 1 1 1 v b v 1 0 00 00 0 0 0 0 0 0 0 000 v bv 0 00 tclk line signal tpdata 0 0 000 1 1 1 1 1 1 1 v b v 1 0 00 00 0 0 0 0 0 0 0 0 00 v 0 0 00 tclk line signal tpdata
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 26 n otes : 1. when dual-rail data format is selected, the b3zs/hdb3 encoder is automatically disabled. 2. in dual-rail format, the bipolar violations in the incoming data stream is converted to valid data pulses. 3. encoder and decoder is enabled only in single-rail mode. 4.3 t ransmit p ulse s haper : the transmit pulse shaper converts the b3zs encoded digital pulses into a single analog alternate mark inversion (ami) pulse that meet the industry standard mask template requirements for sts-1 and ds3. see figure 8 and figure 9. for e3 mode, the pulse shaper converts the hdb3 encoded pulses into a single full amplitude square shaped pulse with very little slope. this is illustrated in figure 7. the pulse shaper block also consists of a transmit build out circuit, which can either be disabled or enabled by setting the txlev input pin high or low (in hardware mode) or setting the txlev bit to 1 or 0 in the control register (in host mode). for ds3/sts-1 rates, the transmit build out circuit is used to shape the transmit waveform that ensures that transmit pulse template requirements are met at the cross-connect system. the distance between the transmitter output and the cross-connect system can be between 0 to 450 feet. for e3 rate, since the output pulse template is measured at the secondary of the transformer and since there is no cross-connect system pulse template requirements, the transmit build out circuit is always disabled. 4.3.1 guidelines for using transmit build out circuit: if the distance between the transmitter and the dsx3 or stsx-1, cross-connect system, is less than 225 feet, enable the transmit build out circuit by setting the txlev input pin low (in hardware mode) or setting the txlev control bit to 0 (in host mode). if the distance between the transmitter and the dsx3 or stsx-1 is greater than 225 feet, disable the transmit build out circuit. 4.3.2 interfacing to the line: the differential line driver increases the transmit waveform to appropriate level and drives into the 75 w load as shown in figure 6. 4.4 transmit drive monitor: this feature is used for monitoring the transmit line for occurrence of fault conditions such as short circuit on the line or defective line driver.the device can also be configured for internal tranmit driver monitoring. to monitor the transmitter output of another chip, connect mtip pin to the ttip line via a 270 w resistor and mring pins to tring line via 270 w resistor as shown in figure 16 in order to configure the device for internal transmit driver monitoring, set the txmon bit to 1 in the transmit control register.
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 27 when the mtip and mring are connected to the ttip and tring lines, the drive monitor circuit monitors the line for transitions. the dmo (drive monitor output) will be asserted low as long as the transitions on the line are detected via mtip and mring. if no transitions on the line are detected for 128 32 txclk periods, the dmo output toggles high and when the transitions are detected again, dmo toggles low. n ote : the drive monitor circuit is only for diagnostic purposes and does not have to be used to operate the transmitter. 4.5 transmitter section on/off: the transmitter section can be turned on or off. to turn on the transmitter in the hardware mode, pull txon pin high. in the host mode, write a 1 to the txon control bit and pull the txon pin high to turn on the transmitter. when the transmitter is turned off, the ttip and tring are tri-stated. n otes : 1. this feature provides support for redundancy. 2. if the XRT75L00D is configured in host mode, to permit a system designed for redundancy to quickly shut-off the defective line card and turn on the back-up line card, writing a 1 to the txon control bit transfers the control to txon pin. 5.0 the receiver section: this section describes the detailed operation of the various blocks in the receiver. the receiver recovers the ttl/cmos level data from the incoming bipolar b3zs or hdb3 encoded input pulses. 5.1 agc/equalizer: the adaptive gain control circuit amplifies the incoming analog signal and compensates for the various flat losses and also for the loss at one-half symbol rate. the agc has a dynamic range of 30 db. the equalizer restores the integrity of the signal and compensates for the frequency dependent attenuation of up to 900 feet of coaxial cable (1300 feet for e3). the equalizer also boosts the high frequency content of the signal to reduce the inter-symbol interference (isi) so that, the slicer slices the signal at 50% of peak voltage to generate positive and negative data. f igure 16. t ransmit d river m onitor set - up . 3.3k w + 1% ttip tring XRT75L00D 1:1 r3 75 w txpos txneg txlineclk tpdata tndata txclk rext refagnd 37.4 w + 1% 37.4 w +1% r1 r2 mring mtip r5 270 w r4 270 w 3.3k w + 1% txpos txneg txlineclk tpdata tndata txclk rext refagnd mring mtip ttip tring r3 75 w 37.4 w + 1% 37.4 w +1% r1 r2 1:1
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 28 the equalizer can either be in or out by setting the reqen pin high or low (in hardware mode) or setting the reqen control bit to 1 or 0 (in host mode). r ecommendations for e qualizer s ettings : the equalizer has two gain settings to provide optimum equalization. in the case of normally shaped ds3/ sts-1 pulses (pulses that meet the template requirements) that has been driven through 0 to 900 feet of cable, the equalizer can be left in by setting the reqen pin to high (in hardware mode) or setting the reqen control bit to 1 (in host mode). however, for square-shaped pulses such as e3 or for ds3/sts-1 high pulses (that does not meet the pulse template requirements), it is recommended that the equalizer be left out for cable length less than 300 feet by setting the reqen pin low (in hardware mode) or by setting the reqen control bit to 0 (in host mode).this would help to prevent over-equalization of the signal and thus optimize the performance in terms of better jitter transfer characteristics. n ote : the results of extensive testing indicates that even when the equalizer was left in (reqen = high), regardless of the cable length, the integrity of the e3 signal was restored properly over 0 to 12 db cable loss at industrial temperature. the equalizer also contain an additional 20 db gain stage to provide the line monitoring capability of the resistively attenuated signals which may have 20db flat loss. this capability can be turned on by writing a 1 to the rxmon bits in the control register or by setting the rxmon pin (pin 27) high. 5.1.1 interference tolerance: for e3 mode, itu-t g.703 recommendation specifies that the receiver be able to recover error-free clock and data in the presence of a sinusoidal interfering tone signal. for ds3 and sts-1 modes, the same recommendation is being used. figure 17 shows the configuration to test the interference margin for ds3/ sts1. figure 18 shows the set up for e3. f igure 17. i nterference m argin t est s et up for ds3/sts-1 sine wave generator pattern generator 2 23 - 1 prbs m attenuator ds3 = 22.368 mhz sts-1 = 25.92 mhz s n cable simulator dut XRT75L00D test equipment
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 29 5.2 clock and data recovery: the clock and data recovery circuit extracts the embedded clock, from the sliced digital data stream and provides the retimed data to the b3zs (hdb3) decoder. the clock recovery pll can be in one of the following two modes: t raining m ode : in the absence of input signals at rtip and rring pins, or when the frequency difference between the recovered line clock signal and the reference clock applied on the exclk input pin exceed 0.5%, the clock recovery unit enters into training mode and a loss of lock condition is declared by toggling rlol output pin high (in hardware mode) or setting the rlol bit to 1 in the control registers (in host mode). also, the clock output on the rxclk pin is the same as the reference clock applied on exclk pin. d ata /c lock r ecovery m ode : in the presence of input line signals on the rtip and rring input pins and when the frequency difference between the recovered clock signal and the reference clock signal is less than 0.5%, the clock that is output on the rxclk out pin is the recovered clock signal. 5.3 b3zs/hdb3 decoder: f igure 18. i nterference m argin t est s et up for e3. t able 9: i nterference m argin t est r esults m ode c able l ength (a ttenuation )i nterference t olerance e3 0 db -14 db 12 db -18 db ds3 0 feet -17 db 225 feet -16 db 450 feet -16 db sts-1 0 feet -16 db 225 feet -15 db 450 feet -15 db noise generator pattern generator m attenuator 1 s n cable simulator dut XRT75L00D test equipment attenuator 2
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 30 the decoder block takes the output from clock and data recovery block and decodes the b3zs (for ds3 or sts-1) or hdb3 (for e3) encoded line signal and detects any coding errors or excessive zeros in the data stream. whenever the input signal violates the b3zs or hdb3 coding sequence for bipolar violation or contains three (for b3zs) or four (for hdb3) or more consecutive zeros, an active high pulse is generated on the rlcv output pins to indicate line code violation. n ote : in single- rail (nrz) mode, the decoder is bypassed. 5.4 los (loss of signal) detector: 5.4.1 ds3/sts-1 los condition: a digital loss of signal (dlos) condition occurs when a string of 175 75 consecutive zeros occur on the line. when the dlos condition occurs, the dlos bit is set to 1 in the status control register. dlos condition is cleared when the detected average pulse density is greater than 33% for 175 75 pulses. analog loss of signal (alos) condition occurs when the amplitude of the incoming line signal is below the threshold as shown in the table 10.the status of the alos condition is reflected in the alos status control register. rlos is the logical or of the dlos and alos states. when the rlos condition occurs the rlos output pin is toggled high and the rlos bit is set to 1 in the status control register. d isabling alos/dlos d etector : for debugging purposes it is useful to disable the alos/dlos detector. writing a 1 to the alos and dlos bits disables the los detector on a per channel basis. 5.4.2 e3 los condition: if the level of incoming line signal drops below the threshold as described in the itu-t g.775 standard, the los condition is detected. loss of signal level is defined to be between 15 and 35 db below the normal level. if the signal drops below 35 db for 175 75 consecutive pulse periods, los condition is declared. this is illustrated in figure 19. t able 10: t he alos (a nalog los) d eclaration and c learance t hresholds for a given setting of reqen (ds3 and sts-1 a pplications ) a pplication reqen s etting s ignal l evel to d eclare alos s ignal l evel to c lear alos ds3 1< 20mv > 90mv sts-1 1< 25mv > 115mv
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 31 as defined in itu-t g.775, an los condition is also declared between 10 and 255 ui (or e3 bit periods) after the actual time the los condition has occurred. the los condition is cleared within 10 to 255 ui after restoration of the incoming line signal. figure 20 shows the los declaration and clearance conditions. 5.4.3 muting the recovered data with los condition: when the los condition is declared, the clock recovery circuit locks into the reference clock applied to the exclk pin and output this clock on the rxclk output. the data on the rpos and rneg pins can be forced to zero by pulling the losmut pin high (in hardware mode) or by setting the losmut bits in the individual channel control register to 1 (in host mode). n ote : when the los condition is cleared, the recovered data is output on rpos and rneg pins. f igure 19. l oss o f s ignal d efinition for e3 as per itu-t g.775 f igure 20. l oss of s ignal d efinition for e3 as per itu-t g.775. 0 db -12 db -15db -35db maximum cable loss for e3 los signal must be declared los signal must be cleared los signal may be cleared or declared actual occurrence of los condition line signal is restored time range for los declaration time range for los clearance g.775 compliance g.775 compliance 0 ui 10 ui 0 ui 10 ui 255 ui 255 ui rtip/ rring rlos output pin
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 32 6.0 jitter: there are three fundamental parameters that describe circuit performance relative to jitter: jitter tolerance (receiver) jitter transfer (receiver/transmitter) jitter generation 6.1 j itter t olerance - r eceiver : jitter tolerance is a measure of how well a clock and data recovery unit can successfully recover data in the presence of various forms of jitter. it is characterized by the amount of jitter required to produce a specified bit error rate. the tolerance depends on the frequency content of the jitter. jitter tolerance is measured as the jitter amplitude over a jitter spectrum for which the clock and data recovery unit achieves a specified bit error rate (ber). to measure the jitter tolerance as shown in figure 21, jitter is introduced by the sinusoidal modulation of the serial data bit sequence. input jitter tolerance requirements are specified in terms of compliance with jitter mask which is represented as a combination of points.each point corresponds to a minimum amplitude of sinusoidal jitter at a given jitter frequency. 6.1.1 ds3/sts-1 jitter tolerance requirements: bellcore gr-499 core, issue 1, december 1995 specifies the minimum requirement of jitter tolerance for category i and category ii. the jitter tolerance requirement for category ii is the most stringent. figure 22 shows the jitter tolerance curve as per gr-499 specification along with the measured performance for the device. f igure 21. j itter t olerance m easurements freq synthesizer freq synthesizer pattern generator pattern generator dut XRT75L00D dut XRT75L00D error detector error detector modulation freq. data clock
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 33 6.1.2 e3 jitter tolerance requirements: itu-t g.823 standard specifies that the clock and data recovery unit must be able to accommodate and tolerate jitter up to certain specified limits. figure 23 shows the tolerance curve and the actual measured data for the device. the figure 11 below shows the jitter amplitude versus the modulation frequency for various standards. f igure 22. i nput j itter t olerance f or ds3/sts-1 f igure 23. i nput j itter t olerance for e3 0.01 0.03 15 1.5 0.3 2 20 0.15 jitter amplitude (ui pp ) jitter frequency (khz) 10 5 0.3 100 0.1 gr-253 sts-1 gr-499 cat ii gr-499 cat i 64 41 XRT75L00D 0.1 1.5 1 10 jitter amplitude (ui pp ) jitter frequency (khz) 800 itu-t g.823 64 10 0.3 XRT75L00D
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 34 6.2 j itter t ransfer - r eceiver /t ransmitter : jitter transfer function is defined as the ratio of jitter on the output relative to the jitter applied on the input versus frequency. there are two distinct characteristics in jitter transfer: jitter gain (jitter peaking) defined as the highest ratio above 0 db; and jitter transfer bandwidth.the overall jitter transfer bandwidth is controller by a low bandwidth loop,which is part of the XRT75L00D. the jitter transfer function is a ratio between the jitter output and jitter input for a component, or system often expressed in db. a negative db jitter transfer indicates the element removed jitter. a positive db jitter transfer indicates the element added jitter.a zero db jitter transfer indicates the element had no effect on jitter. table 12 shows the jitter transfer characteristics and/or jitter attenuation specifications for various data rates: the XRT75L00D meets the above jitter specifications. 6.3 j itter g eneration : jitter generation is defined as the process whereby jitter appears at the output port of the digital equipment in the absence of applied input jitter. jitter generation is measured by sending jitter free data to the clock and data recovery circuit and measuring the amount of jitter on the output clock or the re-timed data. since this is essentially a noise measurement, it requires a definition of bandwidth to be meaningful. the bandwidth is set according to the data rate. in general, the jitter is measured over a band of frequencies. 6.4 jitter attenuator: an advanced crystal-less jitter attenuator is included in the XRT75L00D. the jitter attenuator uses the internal reference clock. in host mode, by clearing or setting the jatx/rx bit in the control register selects the jitter attenuator either in the receive or transmit path. in hardware mode, jatx/rx pin selects the jitter attenuator in receive or transmit path. the fifo is either a 16-bit, 32-bit or 128-bit register. in host mode, the bits ja0 and ja1can be set to appropriate combination to select the different fifo sizes or to disable the jitter attenuator. in hardware mode, appropriate setting of the pins ja0 and ja1 selects the different fifo sizes or disable the jitter attenuator. data is clocked into the fifo with the associated clock signal (txclk or rxclk) and clocked out of the fifo with the dejittered clock. when the fifo is within two bits of overflowing or underflowing, the fifo limit status bit, fl is set to 1 in the alarm status register. reading this bit clears the fifo and resets the bit into default state. t able 11: j itter a mplitude versus m odulation f requency (j itter t olerance ) b it r ate ( kb / s ) s tandard i nput j itter a mplitude (ui p - p ) m odulation f requency a1 a2 a3 f 1(h z ) f 2(h z ) f 3( k h z ) f 4( k h z ) f 5( k h z ) 34368 itu-t g.823 1.5 0.15 - 100 1000 10 800 - 44736 gr-499 core cat i 5 0.1 - 10 2.3k 60 300 - 44736 gr-499 core cat ii 10 0.3 - 10 669 22.3 300 - 51840 gr-253 core cat ii 15 1.5 0.15 10 30 300 2 20 t able 12: j itter t ransfer s pecifications e3 ds3 sts-1 etsi tbr-24 gr-499 core section 7.3.2 category i and category ii gr-253 core section 5.6.2.1
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 35 n ote : it is recommended to select the 16-bit fifo for delay-sensitive applications as well as for removing smaller amounts of jitter. table 13 specifies the jitter transfer mask requirements for various data rates: the jitter attenuator within the XRT75L00D meets the latest jitter attenuation specifications and/or jitter transfer characteristics as shown in the figure 24. t able 13: j itter t ransfer p ass m asks r ate ( kbits ) m ask f1 (h z ) f2 (h z ) f3 (h z ) f4 ( k h z ) a1(db) a2(db) 34368 g.823 etsi-tbr-24 100 300 3 k 800 k 0.5 -19.5 44736 gr-499, cat i gr-499, cat ii gr-253 core 10 10 10 10k 56.6k 40 - - - 15k 300k 15k 0.1 0.1 0.1 - - - 51840 gr-253 core 10 40k - 400k 0.1 - f igure 24. j itter t ransfer r equirements and j itter a ttenuator p erformance f1 a1 f2 jitter amplitude jitter frequency (khz) a2 f3 f4
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 36 7.0 serial host interface: a flexible serial microprocessor interface is incorporated in the XRT75L00D. the interface is generic and is designed to support the common microprocessors/microcontrollers. the XRT75L00D operates in host mode when the host/hw pin is tied high. the serial interface includes a serial clock (sclk), serial data input (sdi), serial data output (sdo), chip select (cs) and interrupt output (int). the serial interface timing is shown in figure 11. the active low interrupt output signal (int pin) indicates alarm conditions like los, dmo and fl to the processor. when the XRT75L00D is configured in host mode, the following input pins,txlev, taos, rlb, llb, e3, sts- 1/ds3, reqen, jatx/rx, ja0 and ja1 are disabled and must be connected to ground. table 14 below illustrates the functions of the shared pins in either host mode or in hardware mode. n ote : while configured in host mode, the txon input pin will be active if the txon bit in the control register is set to 1, and can be used to turn on and off the transmit output drivers. this permits a system designed for redundancy to quickly switch out a defective line card and switch-in the backup line card. t able 14: f unctions of shared pins p in n umber i n h ost m ode i n h ardware m ode 24 cs rxclkinv 26 sclk txclkinv 25 sdi rxon 27 sdo rxmon 28 int losmut t able 15: r egister m ap and b it n ames a ddress (h ex ) p arameter n ame d ata b its 76 5 43210 0x00 aps/redundancy (read/write) reserved reserved reserved rxon reserved reserved reserved txon 0x01 interrupt enable (read/write) reserved cnt_satie prbsie flie rlolie rlosie dmoie 0x02 interrupt status (reset on read) reserved cnt_satis prbsis flis rlolis rlosis dmois 0x03 alarm status (read only) reserved prbsls dlos alos fl rlol rlos dmo 0x04 transmit control (read/write) reserved txmon insprbs reserved taos txclkinv txlev 0x05 receive control (read/write) reserved dlosdis alosdis rxclkinv losmut rxmon reqen 0x06 block control (read/write) reserved prbsen rlb llb e3 sts1/ ds3 sr/dr 0x07 jitter attenuator (read/write) reserved dflck pntrst ja1 jatx/rx ja0
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 37 0x08- 0x1f reserved 0x20 interrupt enable- global (read/write) reserved reserved reserved inten 0x21 interrupt status (read only) reserved reserved reserved intst 0x22- 0x2f reserved reserved 0x30 prbs error count (msb) msb lsb 0x31 prbs error count (lsb) msb lsb 0x32-0x37 reserved 0x38 prbs holding msb lsb 0x39- 0x3d reserved 0x3e chip_id (read only) device part number (7:0) 0x3f chip_version (read only) chip revision number (7:0) t able 16: r egister m ap d escription a ddress (h ex ) t ype b it l ocation s ymbol d escription d efault v alue (b in ) 0x00 r/w d0 rxon bit 4 = rxon, receiver turn on. writing a 1 to the bit field turns on the receiver and a 0 turn off the receiver. 0 d4 txon bit 0 = txon, transmitter turn on. writing a 1 to the bit field turn on the transmitter. writing a 0 turns off the transmitter and tri-state the transmitter output (ttip/tring). 0 t able 15: r egister m ap and b it n ames a ddress (h ex ) p arameter n ame d ata b its 76 5 43210
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 38 0x01 r/w d0 dmoie writing a 1 to this bit field enables the dmo inter- rupt and triggers an interrupt when the transmitter driver fails. writing a 0 disables the interrupt. 0 d1 rlosie writing a 1 to this bit field enables the rlos inter- rupt and triggers an interrupt when the rlos condi- tion occurs. writing a 0 disables the interrupt. 0 d2 rlolie writing a 1 to this bit field enables the rlol inter- rupt and triggers an interrupt when rlol condition occurs. writing a 0 disables the interrupt. 0 d3 flie writing a 1 to this bit field enables the fl interrupt and triggers an interrupt when the fifo limit of the jitter attenuator is within 2 bits of overflow/underflow condition. writing a 0 disables the interrupt. n ote : this bit field is ignored when the jitter attenuator is disabled. 0 d4 prbsie writing a 1 to this bit enables the prbs bit error interrupt. 0 d5 cnt_satie writing a 1 to this bit enables the prbs error- counter saturation interrupt. when the prbs error counter reaches 0xffff, an interrupt will be gener- ated. 0 0x02 reset upon read d0 dmois this bit is set to 1 every time a dmo status change has occurred since the last cleared interrupt.this bit is cleared when read. 0 d1 rlosis this bit is set to 1 every time a rlos status change has occurred since the last cleared interrupt. this bit is cleared when read. 0 d2 rlolis this bit is set to 1 every time a rlol status change has occurred since the last cleared interrupt. this bit is cleared when read. 0 d3 flis this bit is set to 1 every time a fifo limit status change has occurred since the last cleared interrupt. this bit is cleared when read. 0 d4 prbsis this bit is set to 1 when a prbs bit error is detected. this bit is cleared when read. 0 d5 cnt_satis this bit is set to 1 when the prbs error counter has saturated (0xffff). this bit is cleared when read. 0 t able 16: r egister m ap d escription a ddress (h ex ) t ype b it l ocation s ymbol d escription d efault v alue (b in )
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 39 0x03 read only d0 dmo this bit is set to 1 every time the mtip/mring input pins have not detected any bipolar pulses for 128 consecutive bit periods. 0 d1 rlos this bit is set to 1 every time the receiver declares an los condition. 0 d2 rlol this bit is set to 1 every time when the receiver declares a loss of lock condition. 0 d3 fl this bit is set to 1 every time the fifo in the jitter attenuator is within 2 bit of underflow/overflow condi- tion. 0 d4 alos this bit is set to 1 every time the receiver declares analog los condition. 0 d5 dlos this bit is set to 1 every time the receiver declares digital los condition. 0 d6 prbsls this bit is set to 1 every time the prbs detects a bit error. 0 0x04 r/w d0 txlev writing a 1 to this bit disables the transmit build-out circuit and writing a 0 enables the transmit build-out circuit. n ote : see section 4.03 for detailed description. 0 d1 txclkinv writing a 1 to this bit configures the transmitter to sample the data on tpdata/tndata input pins on the rising edge of txclk. 0 d2 taos setting this bit to 1 causes a continuous stream of marks to be sent out at the ttip and tring pins. 0 d3 reserved this bit location is not used. d4 insprbs writing a 1 to this bit causes the prbs generator to insert a single-bit error onto the transmit prbs data stream. n ote : prbs generator/detector must be enabled for this bit to have any effect. 0 d5 txmon when this bit is set to 1, the driver monitor is con- nected to its own transmit channel and monitors the transmit driver. when a transmit failure is detected, the dmo output will go high. when this bit is 0, mtip and mring can be con- nected to other transmit channel for monitoring. 0 t able 16: r egister m ap d escription a ddress (h ex ) t ype b it l ocation s ymbol d escription d efault v alue (b in )
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 40 0x05 r/w d0 reqen setting this bit to 1 enables the receive equalizer . n ote : see section 2.01 for detailed description. 0 d1 rxmon writing a 1 to this bit configures the receiver into monitoring mode. in this mode, the receiver can monitor a signal at the rtip/rring pins that be atten- uated up to 20db flat loss. 0 d2 losmut writing a 1 to this bit causes the rpos/rneg out- puts to be grounded while the los condition is declared. n ote : if this bit has ben set, it will remain set evan after los condition is cleared. 0 d3 rxclkinv writing a 1 to this bit configures the receiver to out- put rpos/rneg data on the falling edge of rxclk. 0 d4 alosdis writing a 1 to this bit disables the alos detector. 0 d5 dlosdis writing a 1 to this bit disables the dlos detector. 0 0x06 r/w d0 sr/dr writing a 1 to this bit configures the receiver and transmitter into single-rail (nrz) mode. 0 d1 sts-1/ds3 writing a 1 to this bit configures the channel 0 into sts-1 mode. n ote : this bit field is ignored if the chip is configured to operate in e3 mode. 0 d2 e3 writing a 1 to this bit configures the chip in e3 mode. 0 d3 llb writing a 1 to this bit configures the chip in local loopback mode. 0 d4 rlb writing a 1 to this bit configures the chip in remote loopback mode. 0 d5 prbsen writing a 1 to this bit enables the prbs generator/ detector.prbs generator generate and detect either 2 15 -1 (ds3 or sts-1) or 2 23 -1 (for e3). the pattern generated and detected are unframed pattern. 0 t able 16: r egister m ap d escription a ddress (h ex ) t ype b it l ocation s ymbol d escription d efault v alue (b in ) rlb 0 0 loopback mode normal operation analog local llb 0 1 1 1 remote digital 0 1
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 41 t able 17: r egister m ap d escription - g lobal 0x07 r/w d0 ja0 this bit along with ja1 bit configures the jitter attenu- ator as shown in the table below. 0 d1 jatx/rx writing a 1 to this bit selects the jitter attenuator in the transmit path. a 0 selects in the receive path. 0 d2 ja1 this bit along with the ja0 configures the jitter atten- uator as shown in the table. 0 d3 pntrst setting this bit to 1 resets the read and write point- ers of the jitter attenuator fifo. 0 d4 dflck set this bit to "1" to disable the sonet aps recov- ery time of the pll. when this bit is "0", the aps recovery time is enabled. this helps to reduce the time for the pll to lock to the incoming frequency when the jitter attenuator switches to narrow band. this is required for sonet to ds-3 mapping/demap- ping de-synchronization applications. 0 0x08 reserved a ddress (h ex ) t ype b it l ocation s ymbol d escription d efault v alue (b in ) 0x20 r/w d0 inten bit 0 = inten writing a 1 to this bit enables the interrupts. 0 0x21 read only d0 intst bit 0 = intst bit is set to 1 if an interrupt service is required. the source level interrupt status register is read to determine the cause of interrupt. 0 0x22 - 0x2f reserved 0x30 reset upon read d[7:0] prbsmsb prbs error counter msb [15:8] 0x31 reset upon read d[7:0] prbslsb prbs error counter lsb [7:0] t able 16: r egister m ap d escription a ddress (h ex ) t ype b it l ocation s ymbol d escription d efault v alue (b in ) ja0 0 0 mode 16 bit fifo 32 bit fifo ja1 0 1 1 1 128 bit fifo 0 1 disable jitter attenuator
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 42 8.0 diagnostic features: 8.1 prbs generator and detector: the XRT75L00D contains an on-chip pseudo random binary sequence (prbs) generator and detector for diagnostic purpose. this feature is only available in host mode. with the prbsen bit = 1, the transmitter will send out prbs of 2 23 -1 in e3 rate or 2 15 -1 in sts-1/ds3 rate. at the same time, the receiver prbs detector is also enabled. when the correct prbs pattern is detected by the receiver, the rneg/lcv pin will go low to indicate prbs synchronization has been achieved. when the prbs detector is not in sync the prbsls bit will be set to 1 and rneg/lcv pin will go high. with the prbs mode enabled, the user can also insert a single bit error by toggling insprbs bit. this is done by writing a 1 to insprbs bit. the receiver at rneg/lcv pin will pulse high for half rxclk cycle for every bit error detected. any subsequent single bit error insertion must be done by first writing a 0 to insprbs bit and followed by a 1. when prbs mode is enabled, the prbs counter starts counting each single bit error. the prbs counter is 16 bits wide. the current value in the counter can be read via two readback operations of the serial i/o registers. 1) either the least significant byte (lsb, address 0x30) or the most significant byte (msb, address 0x31) can be read first. the value of the un-read register will be copied into the holding register (address 0x38) and both the lsb and msb registers will be reset to zero. 2) read the holding register and concatenate the result with the value from the first read operation to get the full 16 bit counter value. when the prbs mode is first enabled, errors will be counted while the receiver logic is synchronizing to the prbs pattern. when rneg/lcv goes low indicating prbs synchronization, reset the counter by reading either the lsb or the msb register. figure 25 shows the status of rneg/lcv pin when the XRT75L00D is configured in prbs mode. 0x32- 0x37 reserved 0x38 read only d[7:0] prbshold prbs holding register 0x39- 0x3d reserved 0x3e read only d[7:0] chip_id this read only register contains device id. 01010001 0x3f read only d[7:0] chip_version this read only register contains chip version number 00000001 a ddress (h ex ) t ype b it l ocation s ymbol d escription d efault v alue (b in )
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 43 8.2 loopbacks: the XRT75L00D offers three loopback modes for diagnostic purposes. in hardware mode, the loopback modes are selected via the rlb and llb pins. in host mode, the rlb and llb bits in the control registers select the loopback modes. f igure 25. prbs mode rclk rneg/lcv sync loss prbs sync single bit error
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 44 8.2.1 analog loopback: in this mode, the transmitter outputs (ttip and tring) are connected internally to the receiver inputs (rtip and rring) as shown in figure 26. data and clock are output at rclk, rpos and rneg pins for the corresponding transceiver. analog loopback exercises most of the functional blocks of the device including the jitter attenuator which can be selected in either the transmit or receive path. XRT75L00D can be configured in analog loopback either in hardware mode via the llb and rlb pins or in host mode via llb and rlb bits in the channel control registers. n otes : 1. in the analog loopback mode, data is also output via ttip and tring pins. 2. signals on the rtip and rring pins are ignored during analog loopback. 8.2.2 digital loopback: the digital loopback function is available either in hardware mode or host mode. when the digital loopback is selected, the transmit clock (txclk) and transmit data inputs (tpdata & tndata) are looped back and output onto the rxclk, rpos and rneg pins as shown in figure 27. the data presented on txclk, tpdata and tndata are not output on the ttip and tring pins.this provides the capability to configure the protection card (in redundancy applications) in digital loopback mode without affecting the traffic on the primary card. n ote : signals on the rtip and rring pins are ignored during digital loopback. f igure 26. a nalog l oopback tring ttip rring rtip rpos rneg rclk tndata tclk tpdata hdb3/b3zs 1 encoder hdb3/b3zs 1 decoder jitter 2 attenuator jitter 2 attenuator timing control data & clock recovery 1 if enabled 2 if enabled and selected in either receive or transmit path tx rx
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 45 8.2.3 remote loopback: with remote loopback activated as shown in figure 28,the receive data on rtip and rring is looped back after the jitter attenuator (if selected in receive or transmit path) to the transmit path using rxclk as transmit timing. the receive data is also output via the rpos and rneg pins. during the remote loopback mode, if the jitter attenuator is selected in the transmit path, the receive data after the clock and data recovery block is looped back to the transmit path and pass through the jitter attenuator using rxclk as the transmit timing. n ote : input signals on txclk, tpdata and tndata are ignored during remote loopback. 8.3 transmit all ones (taos): transmit all ones (taos) can be set either in hardware mode by pulling the taos pins high or in host mode by setting the taos control bits to 1 in the channel control registers. when the taos is set, the transmit section generates and transmits a continuous ami all 1s pattern on ttip and tring pins. the frequency of this 1s pattern is determined by tclk.taos data path is shown in figure 29. f igure 27. d igital l oopback f igure 28. r emote l oopback tring ttip rring rtip rpos rneg rclk tndata tclk tpdata hdb3/b3zs 1 encoder hdb3/b3zs 1 decoder jitter 2 attenuator jitter 2 attenuator timing control data & clock recovery 1 if enabled 2 if enabled and selected in either receive or transmit path tx rx tring ttip rring rtip rpos rneg rclk tndata tclk tpdata hdb3/b3zs 1 encoder hdb3/b3zs 1 decoder jitter 2 attenuator jitter 2 attenuator timing control data & clock recovery 1 if enabled 2 if enabled and selected in either receive or transmit path tx rx
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 46 f igure 29. t ransmit a ll o nes (taos) tring ttip rring rtip rpos rneg rclk tndata tclk tpdata hdb3/b3zs encoder hdb3/b3zs decoder jitter 2 attenuator jitter 2 attenuator timing control data & clock recovery 1 if enabled 2 if enabled and selected in either receive or transmit path tx rx taos transmit all 1 1 1
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 47 9.0 the sonet/sdh de-sync function within the liu the liu with d-sync is very similar to the non d-sync liu in that they both contain jitter attenuator blocks within each channel. they are also pin to pin compatible with each other. however, the jitter attenuators within the d-sync have some enhancements over and above those within the non d-sync device. the jitter attenuator blocks will support all of the modes and features that exist in the non d-sync device and in addition they also support a sonet/sdh de-sync mode. n ote : the "d" suffix within the part number stands for "de-sync". the sonet/sdh de-sync feature of the jitter attenuator blocks permits the user to design a sonet/sdh pte (path terminating equipment) that will comply with all of the following intrinsic jitter and wander requirements. for sonet applications n category i intrinsic jitter requirements per telcordia gr-253-core (for ds3 applications) n ansi t1.105.03b-1997 - sonet jitter at network interfaces - ds3 wander supplement for sdh applications n jitter and wander generation requirements per itu-t g.783 (for ds3 and e3 applications) specifically, if the user designs in the liu along with a sonet/sdh mapper ic (which can be realized as either a standard product or as a custom logic solution, in an asic or fpga), then the following can be accomplished. the mapper can receive an sts-n or an stm-m signal (which is carrying asynchronously-mapped ds3 and/ or e3 signals) and byte de-interleave this data into n sts-1 or 3*m vc-3 signals the mapper will then terminate these sts-1 or vc-3 signals and will de-map out this ds3 or e3 data from the incoming sts-1 spes or vc-3s, and output this ds3 or e3 to the ds3/e3 facility-side towards the liu this ds3 or e3 signal (as it is output from these mapper devices) will contain a large amount of intrinsic jitter and wander due to (1) the process of asynchronously mapping a ds3 or e3 signal into a sonet or sdh signal, (2) the occurrence of pointer adjustments within the sonet or sdh signal (transporting these ds3 or e3 signals) as it traverses the sonet/sdh network, and (3) clock gapping. when the liu has been configured to operate in the "sonet/sdh de-sync" mode, then it will (1) accept this jittery ds3 or e3 clock and data signal from the mapper device (via the transmit system-side interface) and (2) through the jitter attenuator, the liu will reduce the jitter and wander amplitude within these ds3 or e3 signals such that they (when output onto the line) will comply with the above-mentioned intrinsic jitter and wander specifications. 9.1 background and detailed information - sonet de-sync applications this section provides an in-depth discussion on the mechanisms that will cause jitter and wander within a ds3 or e3 signal that is being transported across a sonet or sdh network. a lot of this material is introductory, and can be skipped by the engineer that is already experienced in sonet/sdh designs. in the wide-area network (wan) in north america it is often necessary to transport a ds3 signal over a long distance (perhaps over a thousand miles) in order to support a particular service. now rather than realizing this transport of ds3 data, by using over a thousand miles of coaxial cable (interspaced by a large number of ds3 repeaters) a common thing to do is to route this ds3 signal to a piece of equipment (such as a terminal mux, which in the "sonet community" is known as a pte or path terminating equipment). this terminal mux will asynchronously map the ds3 signal into a sonet signal. at this point, the sonet network will now transport this asynchronously mapped ds3 signal from one pte to another pte (which is located at the other end of the sonet network). once this sonet signal arrives at the remote pte, this ds3 signal will then be extracted from the sonet signal, and will be output to some other ds3 terminal equipment for further processing. similar things are done outside of north america. in this case, this ds3 or e3 signal is routed to a pte, where it is asynchronously mapped into an sdh signal. this asynchronously mapped ds3 or e3 signal is then transported across the sdh network (from one pte to the pte at the other end of the sdh network). once
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 48 this sdh signal arrives at the remote pte, this ds3 or e3 signal will then be extracted from the sdh signal, and will be output to some other ds3/e3 terminal equipment for further processing. figure 30 presents an illustration of this approach to transporting ds3 data over a sonet network as mentioned above a ds3 or e3 signal will be asynchronously mapped into a sonet or sdh signal and then transported over the sonet or sdh network. at the remote pte this ds3 or e3 signal will be extracted (or de-mapped) from this sonet or sdh signal, where it will then be routed to ds3 or e3 terminal equipment for further processing. in order to insure that this "de-mapped" ds3 or e3 signal can be routed to any industry-standard ds3 or e3 terminal equipment, without any complications or adverse effect on the network, the telcordia and itu-t standard committees have specified some limits on both the intrinsic jitter and wander that may exist within these ds3 or e3 signals as they are de-mapped from sonet/sdh. as a consequence, all ptes that maps and de-mapped ds3/e3 signals into/from sonet/sdh must be designed such that the ds3 or e3 data that is de-mapped from sonet/sdh by these ptes must meet these intrinsic jitter and wander requirements. as mentioned above, the liu can assist the system designer (of sonet/sdh pte) by ensuring that their design will meet these intrinsic jitter and wander requirements. this section of the data sheet will present the following information to the user. some background information on mapping ds3/e3 signals into sonet/sdh and de-mapping ds3/e3 signals from sonet/sdh. a brief discussion on the causes of jitter and wander within a ds3 or e3 signal that mapped into a sonet/ sdh signal, and is transported across the sonet/sdh network. a brief review of these intrinsic jitter and wander requirements in both sonet and sdh applications. a brief review on the intrinsic jitter and wander measurement results (of a de-mapped ds3 or e3 signal) whenever the liu device is used in a system design. a detailed discussion on how to design with and configure the liu device such that the end-system will meet these intrinsic jitter and wander requirements. f igure 30. a s imple i llustration of a ds3 signal being mapped into and transported over the sonet n etwork pte pte pte pte sonet network ds3 data ds3 data
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 49 in a sonet system, the relevant specification requirements for intrinsic jitter and wander (within a ds3 signal that is mapped into and then de-mapped from sonet) are listed below. telcordia gr-253-core category i intrinsic jitter requirements for ds3 applications (section 5.6), and ansi t1.105.03b-1997 - sonet jitter at network interfaces - ds3 wander supplement in general, there are three (3) sources of jitter and wander within an asynchronously-mapped ds3 signal that the system designer must be aware of. these sources are listed below. mapping/de-mapping jitter pointer adjustments clock gapping each of these sources of jitter/wander will be defined and discussed in considerable detail within this section. in order to accomplish all of this, this particular section will discuss all of the following topics in details. how ds3 data is mapped into sonet, and how this mapping operation contributes to jitter and wander within this "eventually de-mapped" ds3 signal. how this asynchronously-mapped ds3 data is transported throughout the sonet network, and how occurrences on the sonet network (such as pointer adjustments) will further contributes to jitter and wander within the "eventually de-mapped" ds3 signal. a review of the category i intrinsic jitter requirements (per telcordia gr-253-core) for ds3 applications a review of the ds3 wander requirements per ansi t1.105.03b-1997 a review of the intrinsic jitter and wander capabilities of the liu in a typical system application an in-depth discussion on how to design with and configure the liu to permit the system to the meet the above-mentioned intrinsic jitter and wander requirements n ote : an in-depth discussion on sdh de-sync applications will be presented in the next revision of this data sheet. 9.2 mapping/de-mapping jitter/wander mapping/de-mapping jitter (or wander) is defined as that intrinsic jitter (or wander) that is induced into a ds3 signal by the "asynchronous mapping" process. this section will discuss all of the following aspects of mapping/de-mapping jitter. how ds3 data is mapped into an sts-1 spe how frequency offsets within either the ds3 signal (being mapped into sonet) or within the sts-1 signal itself contributes to intrinsic jitter/wander within the ds3 signal (being transported via the sonet network). 9.2.1 how ds3 data is mapped into sonet whenever a ds3 signal is asynchronously mapped into sonet, this mapping is typically accomplished by a pte accepting ds3 data (from some remote terminal) and then loading this data into certain bit-fields within a given sts-1 spe (or synchronous payload envelope). at this point, this ds3 signal has now been asynchronously mapped into an sts-1 signal. in most applications, the sonet network will then take this particular sts-1 signal and will map it into "higher-speed" sonet signals (e.g., sts-3, sts-12, sts-48, etc.) and will then transport this asynchronously mapped ds3 signal across the sonet network, in this manner. as this "asynchronously-mapped" ds3 signal approaches its "destination" pte, this sts-1 signal will eventually be de-mapped from this sts-n signal. finally, once this sts-1 signal reaches the "destination" pte, then this asynchronously-mapped ds3 signal will be extracted from this sts-1 signal. 9.2.1.1 a brief description of an sts-1 frame in order to be able to describe how a ds3 signal is asynchronously mapped into an sts-1 spe, it is important to define and understand all of the following. the sts-1 frame structure the sts-1 spe (synchronous payload envelope)
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 50 telcordia gr-253-core's recommendation on mapping ds3 data into an sts-1 spe an sts-1 frame is a data-structure that consists of 810 bytes (or 6480 bits). a given sts-1 frame can be viewed as being a 9 row by 90 byte column array (making up the 810 bytes). the frame-repetition rate (for an sts-1 frame) is 8000 frames/second. therefore, the bit-rate for an sts-1 signal is (6480 bits/frame * 8000 frames/sec =) 51.84mbps. a simple illustration of this sonet sts-1 frame is presented below in figure 31. figure 31 indicates that the very first byte of a given sts-1 frame (to be transmitted or received) is located in the extreme upper left hand corner of the 90 column by 9 row array, and that the very last byte of a given sts- 1 frame is located in the extreme lower right-hand corner of the frame structure. whenever a network element transmits a sonet sts-1 frame, it starts by transmitting all of the data, residing within the top row of the sts- 1 frame structure (beginning with the left-most byte, and then transmitting the very next byte, to the right). after the network equipment has completed its transmission of the top or first row, it will then proceed to transmit the second row of data (again starting with the left-most byte, first). once the network equipment has transmitted the last byte of a given sts-1 frame, it will proceed to start transmitting the very next sts-1 frame. the illustration of the sts-1 frame (in figure 31) is very simplistic, for multiple reasons. one major reason is that the sts-1 frame consists of numerous types of bytes. for the sake of discussion within this data sheet, the sts-1 frame will be described as consisting of the following types (or groups) of bytes. the transport overheads (or toh) bytes the envelope capacity bytes 9.2.1.1.1 the transport overhead (toh) bytes the transport overhead or toh bytes occupy the very first three (3) byte columns within each sts-1 frame. figure 32 presents another simple illustration of an sts-1 frame structure. however, in this case, both the toh and the envelope capacity bytes are designated in this figure. f igure 31. a s imple i llustration of the sonet sts-1 f rame sts-1 frame (810 bytes) 90 bytes 9 rows first byte of the sts-1 frame last byte of the sts-1 frame
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 51 since the toh bytes occupy the first three byte columns of each sts-1 frame, and since each sts-1 frame consists of nine (9) rows, then we can state that the toh (within each sts-1 frame) consists of 3 byte columns x 9 rows = 27 bytes. the byte format of the toh is presented below in figure 33. f igure 32. a s imple i llustration of the sts-1 f rame s tructure with the toh and the e nvelope c apacity b ytes d esignated toh envelope capacity 87 bytes 3 bytes 90 bytes 9 row
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 52 in general, the role/purpose of the toh bytes is to fulfill the following functions. to support sts-1 frame synchronization to support error detection within the sts-1 frame to support the transmission of various alarm conditions such as rdi-l (line - remote defect indicator) and rei-l (line - remote error indicator) to support the transmission and reception of "section trace" messages to support the transmission and reception of oam&p messages via the dcc bytes (data communication channel bytes - d1 through d12 byte) the roles of most of the toh bytes is beyond the scope of this data sheet and will not be discussed any further. however, there are a three toh bytes that are important from the stand-point of this data sheet, and will discussed in considerable detail throughout this document. these are the h1 and h2 (e.g., the spe pointer) bytes and the h3 (e.g., the pointer action) byte. figure 34 presents an illustration of the byte-format of the toh within an sts-1 frame, with the h1, h2 and h3 bytes highlighted. f igure 33. t he b yte -f ormat of the toh within an sts-1 f rame a1 a1 b1 b1 d1 d1 h1 h1 b2 b2 d4 d4 s1 s1 d10 d10 d7 d7 c1 c1 f1 f1 d3 d3 h3 h3 k2 k2 d6 d6 e2 e2 d12 d12 d9 d9 a2 a2 e1 e1 d2 d2 h2 h2 k1 k1 d5 d5 m0 m0 d11 d11 d8 d8 envelope capacity bytes envelope capacity bytes 3 byte columns 87 byte columns 9 rows the toh bytes
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 53 although the role of the h1, h2 and h3 bytes will be discussed in much greater detail in section 9.3, jitter/ wander due to pointer adjustments on page 60. for now, we will simply state that the role of these bytes is two-fold. to permit a given pte (path terminating equipment) that is receiving an sts-1 data to be able to locate the sts-1 spe (synchronous payload envelope) within the envelope capacity of this incoming sts-1 data stream and, to inform a given pte whenever pointer adjustment and ndf (new data flag) events occur within the incoming sts-1 data-stream. 9.2.1.1.2 the envelope capacity bytes within an sts-1 frame in general, the envelope capacity bytes are any bytes (within an sts-1 frame) that exist outside of the toh bytes. in short, the envelope capacity contains the sts-1 spe (synchronous payload envelope). in fact, every single byte that exists within the envelope capacity also exists within the sts-1 spe. the only difference that exists between the "envelope capacity" as defined in figure 33 and figure 34 above and the sts-1 spe is that the envelope capacity is aligned with the sts-1 framing boundaries and the toh bytes; whereas the sts-1 spe is not aligned with the sts-1 framing boundaries, nor the toh bytes. the sts-1 spe is an "87 byte column x 9 row" data-structure (which is the exact same size as is the envelope capacity) that is permitted to "float" within the "envelope capacity". as a consequence, the sts-1 spe (within an sts-1 data-stream) will typically straddle across an sts-1 frame boundary. 9.2.1.1.3 the byte structure of the sts-1 spe as mentioned above, the sts-1 spe is an 87 byte column x 9 row structure. the very first column within the sts-1 spe consists of some overhead bytes which are known as the "path overhead" (or poh) bytes. the remaining portions of the sts-1 spe is available for "user" data. the byte structure of the sts-1 spe is presented below in figure 35. f igure 34. t he b yte -f ormat of the toh within an sts-1 f rame a1 a1 b1 b1 d1 d1 h1 h1 b2 b2 d4 d4 s1 s1 d10 d10 d7 d7 c1 c1 f1 f1 d3 d3 h3 h3 k2 k2 d6 d6 e2 e2 d12 d12 d9 d9 a2 a2 e1 e1 d2 d2 h2 h2 k1 k1 d5 d5 m0 m0 d11 d11 d8 d8 envelope capacity bytes envelope capacity bytes 3 byte columns 87 byte columns 9 rows the toh bytes
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 54 in general, the role/purpose of the poh bytes is to fulfill the following functions. to support error detection within the sts-1 spe to support the transmission of various alarm conditions such as rdi-p (path - remote defect indicator) and rei-p (path - remote error indicator) to support the transmission and reception of "path trace" messages the role of the poh bytes is beyond the scope of this data sheet and will not be discussed any further. 9.2.1.2 mapping ds3 data into an sts-1 spe now that we have defined the sts-1 spe, we can now describe how a ds3 signal is mapped into an sts-1 spe. as mentioned above, the sts-1 spe is basically an 87 byte column x 9 row structure of data. the very first byte column (e.g., in all 9 bytes) consists of the poh (path overhead) bytes. all of the remaining bytes within the sts-1 spe is simply referred to as "user" or "payload" data because this is the portion of the sts-1 signal that is used to transport "user data" from one end of the sonet network to the other. telcordia gr- 253-core specifies the approach that one must use to asynchronously map ds3 data into an sts-1 spe. in short, this approach is presented below in figure 36. f igure 35. i llustration of the b yte s tructure of the sts-1 spe z5 z5 z4 z4 z3 z3 h4 h4 f2 f2 g1 g1 c2 c2 b3 b3 j1 j1 payload (or user) data 86 bytes 1 byte 87 bytes 9 rows
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 55 figure 36 was copied directly out of telcordia gr-253-core. however, this figure can be simplified and redrawn as depicted below in figure 37. f igure 36. a n i llustration of t elcordia gr-253-core' s r ecommendation on how map ds3 data into an sts-1 spe f igure 37. a s implified "b it -o riented " v ersion of t elcordia gr-253-core' s r ecommendation on how to map ds3 data into an sts-1 spe ? for ds3 mapping, the sts-1 spe has the following structure. 25i i c3 r 25i i c2 r 25i c1 r r 25i i c3 r 25i i c2 r 25i c1 r r 25i i c3 r 25i i c2 r 25i c1 r r 25i i c3 r 25i i c2 r 25i c1 r r 25i i c3 r 25i i c2 r 25i c1 r r 25i i c3 r 25i i c2 r 25i c1 r r 25i i c3 r 25i i c2 r 25i c1 r r 25i i c3 r 25i i c2 r 25i c1 r r 25i i c3 r 25i i c2 r 25i c1 r r poh 87 bytes r = [r, r, r, r, r, r, r, r] i = [i, i, i, i, i, i, i, i] c1 = [r, r, c, i, i, i, i, i] c2 = [c, c, r, r, r, r, r, r] c3 = [c, c, r, r, o, o, r, s] i = ds3 data r = fixed stuff bit c = stuff control bit s = stuff opportunity bit o = overhead communications channel bit fixed stuff 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r 208i s 1r 2o 2r 2c 16r 208i 6r 2c 16r 205i c 18r r c s i o - fixed stuff bits - stuff control/indicator bits - ds3 data bits - stuff opportunity bits - overhead communication bits poh
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 56 figure 37 presents an alternative illustration of telcordia gr-253-core's recommendation on how to asynchronously map ds3 data into an sts-1 spe. in this case, the sts-1 spe bit-format is expressed purely in the form of "bit-types" and "numbers of bits within each of these types of bits". if one studies this figure closely he/she will notice that this is the same "87 byte column x 9 row" structure that we have been talking about when defining the sts-1 spe. however, in this figure, the "user-data" field is now defined and is said to consist of five (5) different types of bits. each of these bit-types play a role when asynchronously mapping a ds3 signal into an sts-1 spe. each of these types of bits are listed and described below. fixed stuff bits fixed stuff bits are simply "space-filler" bits that simply occupy space within the sts-1 spe. these bit-fields have no functional role other than "space occupation". telcordia gr-253-core does not define any particular value that these bits should be set to. each of the 9 rows, within the sts-1 spe will contain 59 of these "fixed stuff" bits. ds3 data bits the ds3 data-bits are (as its name implies) used to transport the ds3 data-bits within the sts-1 spe. if the sts-1 spe is transporting a framed ds3 data-stream, then these ds3 data bits will carry both the "ds3 payload data" and the "ds3 overhead bits". each of the 9 rows, within the sts-1 spe will contain 621 of these "ds3 data bits". this means that each sts-1 spe contains 5,589 of these ds3 data bit-fields. stuff opportunity bits the "stuff" opportunity bits will function as either a "stuff" (or junk) bit, or it will carry a ds3 data-bit. the decision as to whether to have a "stuff opportunity" bit transport a "ds3 data-bit" or a "stuff" bit depends upon the "timing differences" between the ds3 data that is being mapped into the sts-1 spe and the timing source that is driving the sts-1 circuitry within the pte. as will be described later on, these "stuff opportunity" bits play a very important role in "frequency-justifying" the ds3 data that is being mapped into the sts-1 spe. these "stuff opportunity" bits also play a critical role in inducing intrinsic jitter and wander within the ds3 signal (as it is de-mapped by the remote pte). each of the 9 rows, within the sts-1 spe consists of one (1) stuff opportunity bit. hence, there are a total of nine "stuff opportunity" bits within each sts-1 spe. stuff control/indicator bits each of the nine (9) rows within the sts-1 spe contains five (5) stuff control/indicator bits. the purpose of these "stuff control/indicator" bits is to indicate (to the de-mapping pte) whether the "stuff opportunity" bits (that resides in the same row) is a "stuff" bit or is carrying a ds3 data bit. if all five of these "stuff control/indicator" bits, within a given row are set to "0", then this means that the corresponding "stuff opportunity" bit (e.g., the "stuff opportunity" bit within the same row) is carrying a ds3 data bit. conversely, if all five of these "stuff control/indicator" bits, within a given row are set to "1" then this means that the corresponding "stuff opportunity" bit is carrying a "stuff" bit. overhead communication bits telcordia gr-253-core permits the user to use these two bits (for each row) as some sort of "communications" bit. some mapper devices, such as the xrt94l43 12-channel ds3/e3/sts-1 to sts-12/ stm-1 mapper and the xrt94l33 3-channel ds3/e3/sts-1 to sts-3/stm-1 mapper ic (both from exar corporation) do permit the user to have access to these bit-fields. however, in general, these particular bits can also be thought of as "fixed stuff" bits, that mostly have a "space occupation" function. 9.2.2 ds3 frequency offsets and the use of the "stuff opportunity" bits in order to fully convey the role that the "stuff-opportunity" bits play, when mapping ds3 data into sonet, we will present a detailed discussion of each of the following "mapping ds3 into sts-1" scenarios. the ideal case (e.g., with no frequency offsets) the 44.736mbps + 1 ppm case
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 57 the 44.736mhz - 1ppm case throughout each of these cases, we will discuss how the resulting "bit-stuffing" (that was done when mapping the ds3 signal into sonet) affects the amount of intrinsic jitter and wander that will be present in the ds3 signal, once it is ultimately de-mapped from sonet. 9.2.2.1 the ideal case for mapping ds3 data into an sts-1 signal (e.g., with no frequency offsets) let us assume that we are mapping a ds3 signal, which has a bit rate of exactly 44.736mbps (with no frequency offset) into sonet. further, let us assume that the sonet circuitry within the pte is clocked at exactly 51.84mhz (also with no frequency offset), as depicted below. given the above-mentioned assumptions, we can state the following. the ds3 data-stream has a bit-rate of exactly 44.736mbps the pte will create 8000 sts-1 spe's per second in order to properly map a ds3 data-stream into an sts-1 data-stream, then each sts-1 spe must carry (44.736mbps/8000 =) 5592 ds3 data bits. is there a problem? according to figure 37, each sts-1 spe only contains 5589 bits that are specifically designated for "ds3 data bits". in this case, each sts-1 spe appears to be three bits "short". no there is a simple solution no, earlier we mentioned that each sts-1 spe consists of nine (9) "stuff opportunity" bits. therefore, these three additional bits (for ds3 data) are obtained by using three of these "stuff opportunity" bits. as a consequence, three (3) of these nine (9) "stuff opportunity" bits, within each sts-1 spe, will carry ds3 data- bits. the remaining six (6) "stuff opportunity" bits will typically function as "stuff" bits. in summary, for the "ideal case"; where there is no frequency offset between the ds3 and the sts-1 bit-rates, once this ds3 data-stream has been mapped into the sts-1 data-stream, then each and every sts-1 spe will have the following "stuff opportunity" bit utilization. 3 "stuff opportunity" bits will carry ds3 data bits. 6 "stuff opportunity" bits will function as "stuff" bits in this case, this ds3 signal (which has now been mapped into sts-1) will be transported across the sonet network. as this sts-1 signal arrives at the "destination pte", this pte will extract (or de-map) this ds3 data- stream from each incoming sts-1 spe. now since each and every sts-1 spe contains exactly 5592 ds3 data bits; then the bit rate of this ds3 signal will be exactly 44.736mbps (such as it was when it was mapped into sonet, at the "source" pte). f igure 38. a s imple i llustration of a ds3 d ata -s tream being m apped into an sts-1 spe, via a pte pte pte 44.736mhz + 0ppm ds3_data_in sts-1_data_out 51.84mhz + 0ppm
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 58 as a consequence, no "mapping/de-mapping" jitter or wander is induced in the "ideal case". 9.2.2.2 the 44.736mbps + 1ppm case the "above example" was a very ideal case. in reality, there are going to be frequency offsets in both the ds3 and sts-1 signals. for instance bellcore gr-499-core mandates that a ds3 signal have a bit rate of 44.736mbps 20ppm. hence, the bit-rate of a "bellcore" compliant ds3 signal can vary from the exact correct frequency for ds3 by as much of 20ppm in either direction. similarly, many sonet applications mandate that sonet equipment use at least a "stratum 3" level clock as its timing source. this requirement mandates that an sts-1 signal must have a bit rate that is in the range of 51.84 4.6ppm. to make matters worse, there are also provisions for sonet equipment to use (what is referred to as) a "sonet minimum clock" (smc) as its timing source. in this case, an sts-1 signal can have a bit-rate in the range of 51.84mbps 20ppm. in order to convey the impact that frequency offsets (in either the ds3 or sts-1 signal) will impose on the bit- stuffing behavior, and the resulting bit-rate, intrinsic jitter and wander within the ds3 signal that is being transported across the sonet network; let us assume that a ds3 signal, with a bit-rate of 44.736mbps + 1ppm is being mapped into an sts-1 signal with a bit-rate of 51.84mbps + 0ppm. in this case, the following things will occur. in general, most of the sts-1 spe's will each transport 5592 ds3 data bits. however, within a "one-second" period, a ds3 signal that has a bit-rate of 44.736mbps + 1 ppm will deliver approximately 44.7 additional bits (over and above that of a ds3 signal with a bit-rate of 44.736mbps + 0 ppm). this means that this particular signal will need to "negative-stuff" or map in an additional ds3 data bit every (1/44.736 =) 22.35ms. in other words, this additional ds3 data bit will need to be mapped into about one in every (22.35ms 8000 =) 178.8 sts-1 spes in order to avoid dropping any ds3 data-bits. what does this mean at the "source" pte? all of this means that as the "source" pte maps this ds3 signal, with a data rate of 44.736mbps + 1ppm into an sts-1 signal, most of the resulting "outbound" sts-1 spes will transport 5592 ds3 data bits (e.g., 3 stuff opportunity bits will be carrying ds3 data bits, the remaining 6 stuff opportunity bits are "stuff" bits, as in the "ideal" case). however, in approximately one out of 178.8 "outbound" sts-1 spes, there will be a need to insert an additional ds3 data bit within this sts-1 spe. whenever this occurs, then (for these particular sts- 1 spes) the spe will be carrying 5593 ds3 data bits (e.g., 4 stuff opportunity bits will be carrying ds3 data bits, the remaining 5 stuff opportunity bits are "stuff" bits). figure 39 presents an illustration of the sts-1 spe traffic that will be generated by the "source" pte, during this condition. f igure 39. a n i llustration of the sts-1 spe traffic that will be generated by the "s ource " pte, when mapping in a ds3 signal that has a bit rate of 44.736m bps + 1 ppm , into an sts-1 signal source pte source pte 44.736mbps + 1ppm 5592 ds3 data bits 5592 ds3 data bits 5592 ds3 data bits 5592 ds3 data bits spe # n spe # n+1 5592 ds3 data bits 5592 ds3 data bits spe # n+177 5593 ds3 data bits 5593 ds3 data bits 5592 ds3 data bits 5592 ds3 data bits spe # n+178 spe # n+179 extra ds3 data bit stuffed here sts-1 spe data stream
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 59 what does this mean at the "destination" pte? in this case, this ds3 signal (which has now been mapped into an sts-1 data-stream) will be transported across the sonet network. as this sts-1 signal arrives at the "destination" pte, this pte will extract (or de- map) this ds3 data from each incoming sts-1 spe. now, in this case most (e.g., 177/178.8) of the incoming sts-1 spes will contain 5592 ds3 data-bits. therefore, the nominal data rate of the ds3 signal being de- mapped from sonet will be 44.736mbps. however, in approximately 1 out of every 178 incoming sts-1 spes, the spe will carry 5593 ds3 data-bits. this means that (during these times) the data rate of the de- mapped ds3 signal will have an instantaneous frequency that is greater than 44.736mbps. these "excursion" of the de-mapped ds3 data-rate, from the nominal ds3 frequency can be viewed as occurrences of "mapping/ de-mapping" jitter. since each of these "bit-stuffing" events involve the insertion of one ds3 data bit, we can say that the amplitude of this "mapping/de-mapping" jitter is approximately 1ui-pp. from this point on, we will be referring to this type of jitter (e.g., that which is induced by the mapping and de-mapping process) as "de- mapping" jitter. since this occurrence of "de-mapping" jitter is periodic and occurs once every 22.35ms, we can state that this jitter has a frequency of 44.7hz. 9.2.2.3 the 44.736mbps - 1ppm case in this case, let us assume that a ds3 signal, with a bit-rate of 44.736mbps - 1ppm is being mapped into an sts-1 signal with a bit-rate of 51.84mbps + 0ppm. in this case, the following this will occur. in general, most of the sts-1 spes will each transport 5592 ds3 data bits. however, within a "one-second" period a ds3 signal that has a bit-rate of 44.736mbps - 1ppm will deliver approximately 45 too few bits below that of a ds3 signal with a bit-rate of 44.736mbps + 0ppm. this means that this particular signal will need to "positive-stuff" or exclude a ds3 data bit from mapping every (1/44.736) = 22.35ms. in other words, we will need to avoid mapping this ds3 data-bit about one in every (22.35ms*8000) = 178.8 sts-1 spes. what does this mean at the "source" pte? all of this means that as the "source" pte maps this ds3 signal, with a data rate of 44.736mbps - 1ppm into an sts-1 signal, most of the resulting "outbound" sts-1 spes will transport 5592 ds3 data bits (e.g., 3 stuff opportunity bits will be carrying ds3 data bits, the remaining 6 stuff opportunity bits are "stuff" bits). however, in approximately one out of 178.8 "outbound" sts-1 spes, there will be a need for a "positive-stuffing" event. whenever these "positive-stuffing" events occur then (for these particular sts-1 spes) the spe will carry only 5591 ds3 data bits (e.g., in this case, only 2 stuff opportunity bits will be carrying ds3 data-bits, and the remaining 7 stuff opportunity bits are "stuff" bits). figure 40 presents an illustration of the sts-1 spe traffic that will be generated by the "source" pte, during this condition.
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 60 what does this mean at the destination pte? in this case, this ds3 signal (which has now been mapped into an sts-1 data-stream) will be transported across the sonet network. as this sts-1 signal arrives at the "destination" pte, this pte will extract (or de- map) this ds3 data from each incoming sts-1 spe. now, in this case, most (e.g., 177/178.8) of the incoming sts-1 spes will contain 5592 ds3 data-bits. therefore, the nominal data rate of the ds3 signal being de- mapped from sonet will be 44.736mbps. however, in approximately 1 out of every 178 incoming sts-1 spes, the spe will carry only 5591 ds3 data bits. this means that (during these times) the data rate of the de- mapped ds3 signal will have an instantaneous frequency that is less than 44.736mbps. these "excursions" of the de-mapped ds3 data-rate, from the nominal ds3 frequency can be viewed as occurrences of mapping/de- mapping jitter with an amplitude of approximately 1ui-pp. since this occurrence of "de-mapping" jitter is periodic and occurs once every 22.35ms, we can state that this jitter has a frequency of 44.7hz. we talked about de-mapping jitter, what about de-mapping wander? the telcordia and bellcore specifications define "wander" as "jitter with a frequency of less than 10hz". based upon this definition, the ds3 signal (that is being transported by sonet) will cease to contain jitter and will now contain "wander", whenever the frequency offset of the ds3 signal being mapped into sonet is less than 0.2ppm. 9.3 jitter/wander due to pointer adjustments in the previous section, we described how a ds3 signal is asynchronously-mapped into sonet, and we also defined "mapping/de-mapping" jitter. in this section, we will describe how occurrences within the sonet network will induce jitter/wander within the ds3 signal that is being transported across the sonet network. in order to accomplish this, we will discuss the following topics in detail. the concept of an sts-1 spe pointer the concept of pointer adjustments the causes of pointer adjustments how pointer adjustments induce jitter/wander within a ds3 signal being transported by that sonet network. 9.3.1 the concept of an sts-1 spe pointer as mentioned earlier, the sts-1 spe is not aligned to the sts-1 frame boundaries and is permitted to "float" within the envelope capacity. as a consequence, the sts-1 spe will often times "straddle" across two f igure 40. a n i llustration of the sts-1 spe traffic that will be generated by the s ource pte, when mapping a ds3 signal that has a bit rate of 44.736m bps - 1 ppm , into an sts-1 signal source pte source pte 44.736mbps - 1ppm 5592 ds3 data bits 5592 ds3 data bits 5592 ds3 data bits 5592 ds3 data bits spe # n spe # n+1 5592 ds3 data bits 5592 ds3 data bits spe # n+177 5591 ds3 data bits 5591 ds3 data bits 5592 ds3 data bits 5592 ds3 data bits spe # n+178 spe # n+179 ds3 data bit excluded here sts-1 spe data stream
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 61 consecutive sts-1 frames. figure 41 presents an illustration of an sts-1 spe straddling across two consecutive sts-1 frames. a pte that is receiving and terminating an sts-1 data-stream will perform the following tasks. it will acquire and maintain sts-1 frame synchronization with the incoming sts-1 data-stream. once the pte has acquired sts-1 frame synchronization, then it will locate the j1 byte (e.g., the very byte within the very next sts-1 spe) within the envelope capacity by reading out the contents of the h1 and h2 bytes. the h1 and h2 bytes are referred to (in the sonet standards) as the spe pointer bytes. when these two bytes are concatenated together in order to form a 16-bit word (with the h1 byte functioning as the "most significant byte") then the contents of the "lower" 10 bit-fields (within this 16-bit word) reflects the location of the j1 byte within the envelope capacity of the incoming sts-1 data-stream. figure 42 presents an illustration of the bit format of the h1 and h2 bytes, and indicates which bit-fields are used to reflect the location of the j1 byte. f igure 41. a n i llustration of an sts-1 spe straddling across two consecutive sts-1 frames toh sts-1 frame n sts-1 frame n + 1 j1 byte (1 st byte of spe) j1 byte (1 st byte of next spe) h1, h2 bytes spe can straddle across two sts-1 frames
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 62 figure 43 relates the contents within these 10 bits (within the h1 and h2 bytes) to the location of the j1 byte (e.g., the very first byte of the sts-1 spe) within the envelope capacity. n otes : 1. if the content of the "pointer bits" is "0x00" then the j1 byte is located immediately after the h3 byte, within the envelope capacity. 2. if the contents of the 10-bit expression exceed the value of 0x30f (or 782, in decimal format) then it does not contain a valid pointer value. 9.3.2 pointer adjustments within the sonet network the word sonet stands for "synchronous optical network. this name implies that the entire sonet network is synchronized to a single clock source. however, because the sonet (and sdh) networks can f igure 42. t he b it - format of the 16-b it w ord ( consisting of the h1 and h2 bytes ) with the 10 bits , reflecting the location of the j1 byte , designated f igure 43. t he r elationship between the c ontents of the "p ointer b its " ( e . g ., the 10- bit expression within the h1 and h2 bytes ) and the l ocation of the j1 b yte within the e nvelope c apacity of an sts- 1 f rame x x x x x x x x x x s s n n n n lsb msb h2 byte h1 byte 10 bit pointer expression 521 520 * * * * * * * * * * 436 435 e2 m0 s1 434 433 * * * * * * * * * * 349 348 d12 d11 d10 347 346 * * * * * * * * * * 262 261 d9 d8 d7 260 259 * * * * * * * * * * 175 174 d6 d5 d4 173 172 * * * * * * * * * * 88 87 k2 k1 b2 86 85 * * * * * * * * * * 1 0 h3 h2 h1 782 781 * * * * * * * * * * 697 696 d3 d2 d1 695 694 * * * * * * * * * * 610 609 f1 e1 b1 608 607 * * * * * * * * * * 523 522 c1/j0 a2 a1 toh the pointer value 0 is immediately after the h3 byte
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 63 span thousands of miles, traverse many different pieces of equipments, and even cross international boundaries; in practice, the sonet/sdh network is not synchronized to a single clock source. in practice, the sonet/sdh network can be thought of as being divided into numerous "synchronization islands". each of these "synchronization islands" will consist of numerous pieces of sonet terminal equipment. each of these pieces of sonet terminal equipment will all be synchronized to a single stratum-1 clock source which is the most accurate clock source within the synchronization island. typically a "synchronization island" will consist of a single "timing master" equipment along with multiple "timing slave" pieces of equipment. this "timing master" equipment will be directly connected to the stratum-1 clock source and will have the responsibility of distributing a very accurate clock signal (that has been derived from the stratum 1 clock source) to each of the "timing slave" pieces of equipment within the "synchronization island". the purpose of this is to permit each of the "timing slave" pieces of equipment to be "synchronized" with the "timing master" equipment, as well as the stratum 1 clock source. typically this "clock distribution" is performed in the form of a bits (building integrated timing supply) clock, in which a very precise clock signal is provided to the other pieces of equipment via a t1 or e1 line signal. many of these "synchronization islands" will use a stratum-1" clock source that is derived from gps pulses that are received from satellites that operate at geo-synchronous orbit. other "synchronization islands" will use a stratum-1" clock source that is derived from a very precise local atomic clock. as a consequence, different "synchronization islands" will use different stratum 1 clock sources. the up-shot of having these "synchronization islands" that use different "stratum-1 clock" sources, is that the stratum 1 clock frequencies, between these "synchronization islands" are likely to be slightly different from each other. these "frequency- differences" within stratum 1 clock sources will result in "clock-domain changes" as a sonet signal (that is traversing the sonet network) passes from one "synchronization island" to another. the following section will describe how these "frequency differences" will cause a phenomenon called "pointer adjustments" to occur in the sonet network. 9.3.3 causes of pointer adjustments the best way to discuss how pointer adjustment events occur is to consider an sts-1 signal, which is driven by a timing reference of frequency f1; and that this sts-1 signal is being routed to a network equipment (that resides within a different "synchronization island") and processes sts-1 data at a frequency of f2. n ote : clearly, both frequencies f1 and f2 are at the sts-1 rate (e.g., 51.84mhz). however, these two frequencies are likely to be slightly different from each other. now, since the sts-1 signal (which is of frequency f1) is being routed to the network element (which is operating at frequency f2), the typical design approach for handling "clock-domain" differences is to route this sts-1 signal through a "slip buffer" as illustrated below.
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 64 in the "slip buffer, the "input" sts-1 data (labeled "sts-1 data_in") is latched into the fifo, upon a given edge of the corresponding "sts-1 clock_f1" input clock signal. the sts-1 data (labeled "sts-1 data_out") is clocked out of the slip buffer upon a given edge of the "sts-1 clock_f2" input clock signal. the behavior of the data, passing through the "slip buffer" is now described for each possible relationship between frequencies f1 and f2. if f1 = f2 if both frequencies, f1 and f2 are exactly equal, then the sts-1 data will be "clocked" into the "slip buffer" at exactly the same rate that it is "clocked out". in this case, the "slip buffer" will neither fill-up nor become depleted. as a consequence, no pointer-adjustments will occur in this sts-1 data stream. in other words, the sts-1 spe will remain at a constant location (or offset) within each sts-1 envelope capacity for the duration that this sts-1 signal is supporting this particular service. if f1 < f2 if frequency f1 is less than f2, then this means that the sts-1 data is being "clocked out" of the "slip buffer" at a faster rate than it is being clocked in. in this case, the "slip buffer" will eventually become depleted. whenever this occurs, a typical strategy is to "stuff" (or insert) a "dummy byte" into the data stream. the purpose of stuffing this "dummy byte" is to compensate for the frequency differences between f1 and f2, and attempt to keep the "slip buffer, at a somewhat constant fill level. n ote : this "dummy byte" does not carry any valuable information (not for the user, nor for the system). since this "dummy byte" carries no useful information, it is important that the "receiving pte" be notified anytime this "dummy byte" stuffing occurs. this way, the receiving terminal can "know" not to treat this "dummy byte" as user data. byte-stuffing and pointer incrementing in a sonet network whenever this "byte-stuffing" occurs then the following other things occur within the sts-1 data stream. during the sts-1 frame that contains the "byte-stuffing" event a. the "stuff-byte" will be inserted into the byte position immediately after the h3 byte. this insertion of the "dummy byte" immediately after the h3 byte position will cause the j1 byte (and in-turn, the rest of the spe) to be "byte-shifted" away from the h3 byte. as a consequence, the offset between the h3 byte posi- tion and the sts-1 spe will now have been increased by 1 byte. b. the "transmitting" network equipment will notify the remote terminal of this byte-stuffing event, by invert- ing certain bits within the "pointer word" (within the h1 and h2 bytes) that are referred to as "i" bits. f igure 44. a n i llustration of an sts-1 signal being processed via a s lip b uffer slip buffer slip buffer sts-1 data_in sts-1 clock_f1 sts-1 data_out sts-1 clock_f2 clock domain operating at frequency f1 clock domain operating at frequency f2.
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 65 figure 45 presents an illustration of the bit-format within the 16-bit word (consist of the h1 and h2 bytes) with the "i" bits designated. n ote : at this time the "i" bits are inverted in order to denote that an "incrementing" pointer adjustment event is currently occurring. during the sts-1 frame that follows the "byte-stuffing" event the "i" bits (within the "pointer-word") will be set back to their normal value; and the contents of the h1 and h2 bytes will be incremented by "1". if f1 > f2 if frequency f1 is greater than f2, then this means that the sts-1 data is being clocked into the "slip buffer" at a faster rate than is being clocked out. in this case, the "slip buffer" will start to fill up. whenever this occurs, a typical strategy is to delete (e.g., negative-stuff) a byte from the slip buffer. the purpose of this "negative- stuffing" is to compensate for the frequency differences between f1 and f2; and to attempt to keep the "slip buffer" at a somewhat constant fill-level. n ote : this byte, which is being "un-stuffed" does carry valuable information for the user (e.g., this byte is typically a payload byte). therefore, whenever this negative stuffing occurs, two things must happen. a. the "negative-stuffed" byte must not be simply discarded. in other words, it must somehow also be transmitted to the remote pte with the remainder of the spe data. b. the remote pte must be notified of the occurrence of these "negative-stuffing" events. further, the remote pte must know where to obtain this "negative-stuffed" byte. negative-stuffing and pointer-decrementing in a sonet network whenever this "byte negative-stuffing" occurs then the following other things occur within the sts-1 data- stream. during the sts-1 frame that contains the "negative byte-stuffing" event a. the "negative-stuffed" byte will be inserted into the h3 byte position. whenever an spe data byte is inserted into the h3 byte position (which is ordinarily an unused byte), the number of bytes that will exist between the h3 byte and the j1 byte within the very next spe will be reduced by 1 byte. as a consequence, in this case, the j1 byte (and in-turn, the rest of the spe) will now be "byte-shifted" towards the h3 byte position. b. the "transmitting" network element will notify the remote terminal of this "negative-stuff" event by inverting certain bits within the "pointer word" (within the h1 and h2 bytes) that are referred to as "d" bits. f igure 45. a n i llustration of the b it f ormat within the 16- bit word ( consisting of the h1 and h2 bytes ) with the "i" bits designated d i d i d i d i d i s s n n n n lsb msb h2 byte h1 byte 10 bit pointer expression
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 66 figure 46 presents an illustration of the bit format within the 16-bit word (consisting of the h1 and h2 bytes) with the "d" bits designated. n ote : at this time the "d" bits are inverted in order to denote that a "decrementing" pointer adjustment event is currently occurring. during the sts-1 frame that follows the "negative byte-stuffing" event the "d" bits (within the pointer-word) will be set back to their normal value; and the contents of the h1 and h2 bytes will be decremented by one. f igure 46. a n i llustration of the b it -f ormat within the 16- bit word ( consisting of the h1 and h2 bytes ) with the "d" bits designated d i d i d i d i d i s s n n n n lsb msb h2 byte h1 byte 10 bit pointer expression
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 67 9.3.4 why are we talking about pointer adjustments? the overall sonet network consists of numerous "synchronization islands". as a consequence, whenever a sonet signal is being transmitted from one "synchronization island" to another; that sonet signal will undergo a "clock domain" change as it traverses the network. this clock domain change will result in periodic pointer-adjustments occurring within this sonet signal. depending upon the direction of this "clock-domain" shift that the sonet signal experiences, there will either be periodic "incrementing" pointer-adjustment events or periodic "decrementing" pointer-adjustment events within this sonet signal. regardless of whether a given sonet signal is experiencing incrementing or decrementing pointer adjustment events, each pointer adjustment event will result in an abrupt 8-bit shift in the position of the spe within the sts-1 data-stream. if this sts-1 signal is transporting an "asynchronously-mapped" ds3 signal; then this 8-bit shift in the location of the spe (within the sts-1 signal) will result in approximately 8uipp of jitter within the asynchronously-mapped ds3 signal, as it is de-mapped from sonet. in section 9.5, a review of the category i intrinsic jitter requirements (per telcordia gr-253-core) for ds3 applications on page 68 we will discuss the "category i intrinsic jitter requirements (for ds3 applications) per telcordia gr-253- core. however, for now we will simply state that this 8uipp of intrinsic jitter far exceeds these "intrinsic jitter" requirements. in summary, pointer-adjustments events are a "fact of life" within the sonet/sdh network. further, pointer- adjustment events, within a sonet signal that is transporting an asynchronously-mapped ds3 signal, will impose a significant impact on the intrinsic jitter and wander within that ds3 signal as it is de-mapped from sonet. 9.4 clock gapping jitter in most applications (in which the liu will be used in a sonet de-sync application) the user will typically interface the liu to a mapper device in the manner as presented below in figure 47. in this application, the mapper ic will have the responsibility of receiving an sts-n signal (from the sonet network) and performing all of the following operations on this sts-n signal. byte-de-interleaving this incoming sts-n signal into n sts-1 signals terminating each of these sts-1 signals extracting (or de-mapping) the ds3 signal(s) from the spes within each of these terminated sts-1 signals. in this application, these mapper devices can be thought of as multi-channel devices. for example, an sts-3 mapper can be viewed as a 3-channel ds3/sts-1 to sts-3 mapper ic. similarly, an sts-12 mapper can be f igure 47. i llustration of the t ypical a pplications for the liu in a sonet d e -s ync a pplication ds3 to sts-n mapper/ demapper ic ds3 to sts-n mapper/ demapper ic liu liu sts-n signal tpdata_n input pin tclk_n input de-mapped (gapped) ds3 data and clock
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 68 viewed as a 12-channel ds3/sts-1 to sts-12 mapper ic. continuing on with this line of thought, if a mapper ic is configured to receive an sts-n signal, and (from this sts-n signal) de-map and output n ds3 signals (towards the ds3 facility), then it will typically do so in the following manner. in many cases, the mapper ic will output this ds3 signal, using both a "data-signal" and a "clock-signal". in many cases, the mapper ic will output the contents of an entire sts-1 data-stream via the data-signal. however, as the mapper ic output this sts-1 data-stream, it will typically supply clock pulses (via the clock- signal output) coincident to whenever a ds3 bit is being output via the data-signal. in this case, the mapper ic will not supply a clock pulse coincident to when a toh, poh, or any "non-ds3 data-bit" is being output via the "data-signal". now, since the mapper ic will output the entire sts-1 data stream (via the data-signal), the output clock- signal will be of the form such that it has a period of 19.3ns (e.g., a 51.84mhz clock signal). however, the mapper ic will still generate approximately 44,736,000 clock pulses during any given one second period. hence, the clock signal that is output from the mapper ic will be a horribly gapped 44.736mhz clock signal. one can view such a clock signal as being a very-jittery 44.736mhz clock signal. this jitter that exists within the "clock-signal" is referred to as "clock-gapping" jitter. a more detailed discussion on how the user must handle this type of jitter is presented in section 9.8.2, recommendations on pre-processing the gapped clocks (from the mapper/asic device) prior to routing this ds3 clock and data-signals to the transmit inputs of the liu on page 79. 9.5 a review of the category i intrinsic jitter requirements (per telcordia gr-253-core) for ds3 applications the "category i intrinsic jitter requirements" per telcordia gr-253-core (for ds3 applications) mandates that the user perform a large series of tests against certain specified "scenarios". these "scenarios" and their corresponding requirements is summarized in table 18, below. t able 18: s ummary of "c ategory i i ntrinsic j itter r equirement per t elcordia gr-253-core, for ds3 applications s cenario d escription s cenario n umber t elcordia gr-253-core c ategory i i ntrinsic j itter r equirements c omments ds3 de-mapping jitter 0.4ui-pp includes effects of de-mapping and clock gapping jitter single pointer adjustment a1 0.3ui-pp + ao includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments.note: ao is the amount of intrinsic jitter that was measured during the "ds3 de- mapping jitter" phase of the test. pointer bursts a2 1.3ui-pp includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments. phase transients a3 1.2ui-pp includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments. 87-3 pattern a4 1.0ui-pp includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments. 87-3 add a5 1.3ui-pp includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments. 87-3 cancel a5 1.3ui-pp includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments. continuous pattern a4 1.0ui-pp includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments.
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 69 n ote : all of these intrinsic jitter measurements are to be performed using a band-pass filter of 10hz to 400khz. each of the scenarios presented in table 18, are briefly described below. 9.5.1 ds3 de-mapping jitter ds3 de-mapping jitter is the amount of intrinsic jitter that will be measured within the "line" or "facility-side" ds3 signal, (after it has been de-mapped from a sonet signal) without the occurrence of "pointer adjustments" within the sonet signal. telcordia gr-253-core requires that the "ds3 de-mapping" jitter be less than 0.4ui-pp, when measured over all possible combinations of ds3 and sts-1 frequency offsets. 9.5.2 single pointer adjustment telcordia gr-253-core states that if each pointer adjustment (within a continuous stream of pointer adjustments) is separated from each other by a period of 30 seconds, or more; then they are sufficiently isolated to be considered "single-pointer adjustments". figure 48 presents an illustration of the "single pointer adjustment" scenario. telcordia gr-253-core states that the intrinsic jitter that is measured (within the ds3 signal) that is ultimately de-mapped from a sonet signal that is experiencing "single-pointer adjustment" events, must not exceed the value 0.3ui-pp + ao. n otes : 1. ao is the amount of intrinsic jitter that was measured during the "de-mapping" jitter portion of this test. 2. testing must be performed for both incrementing and decrementing pointer adjustments. 9.5.3 pointer burst figure 49 presents an illustration of the "pointer burst" pointer adjustment scenario per telcordia gr-253- core. continuous add a5 1.3ui-pp includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments. continuous cancel a5 1.3ui-pp includes effects of jitter from clock-gapping, de-map- ping and pointer adjustments. f igure 48. i llustration of s ingle p ointer a djustment s cenario t able 18: s ummary of "c ategory i i ntrinsic j itter r equirement per t elcordia gr-253-core, for ds3 applications s cenario d escription s cenario n umber t elcordia gr-253-core c ategory i i ntrinsic j itter r equirements c omments initialization cool down measurement period > 30s pointer adjustment events
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 70 telcordia gr-253-core mandates that the intrinsic jitter, within the ds3 signal that is de-mapped from a sonet signal, which is experiencing the "burst of pointer adjustment" scenario, must not exceed 1.3ui-pp. 9.5.4 phase transients figure 50 presents an illustration of the "phase transients" pointer adjustment scenario per telcordia gr- 253-core. telcordia gr-253-core mandates that the intrinsic jitter, within the ds3 signal that is de-mapped from a sonet signal, which is experiencing the "phase transient - pointer adjustment" scenario must not exceed 1.2ui-pp. f igure 49. i llustration of b urst of p ointer a djustment s cenario f igure 50. i llustration of "p hase -t ransient " p ointer a djustment s cenario initialization cool down measurement period > 30s pointer adjustment events 0.5ms t pointer adjustment burst train 0.5ms initialization cool down measurement period > 30s pointer adjustment events 0.25s t pointer adjustment burst train 0.25s 0.5s
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 71 9.5.5 87-3 pattern figure 51 presents an illustration of the "87-3 continuous pattern" pointer adjustment scenario per telcordia gr-253-core. telcordia gr-253-core defines an "87-3 continuous" pointer adjustment pattern, as a repeating sequence of 90 pointer adjustment events. within this 90 pointer adjustment event, 87 pointer adjustments are actually executed. the remaining 3 pointer adjustments are never executed. the spacing between individual pointer adjustment events (within this scenario) can range from 7.5ms to 10seconds. telcordia gr-253-core mandates that the intrinsic jitter, within the ds3 signal that is de-mapped from a sonet signal, which is experiencing the "87-3 continuous" pattern of pointer adjustments, must not exceed 1.0ui-pp. 9.5.6 87-3 add figure 52 presents an illustration of the "87-3 add pattern" pointer adjustment scenario per telcordia gr-253- core. f igure 51. a n i llustration of the 87-3 c ontinuous p ointer a djustment p attern initialization measurement period repeating 87-3 pattern (see below) pointer adjustment events 87-3 pattern 87 pointer adjustment events no pointer adjustments t note: t ranges from 34ms to 10s (req) t ranges from 7.5ms to 34ms (obj)
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 72 telcordia gr-253-core defines an "87-3 add" pointer adjustment, as the "87-3 continuous" pointer adjustment pattern, with an additional pointer adjustment inserted, as shown above in figure 52. telcordia gr-253-core mandates that the intrinsic jitter, within the ds3 signal that is de-mapped from a sonet signal, which is experiencing the "87-3 add" pattern of pointer adjustments, must not exceed 1.3ui-pp. 9.5.7 87-3 cancel figure 53 presents an illustration of the 87-3 cancel pattern pointer adjustment scenario per telcordia gr- 253-core. f igure 52. i llustration of the 87-3 a dd p ointer a djustment p attern f igure 53. i llustration of 87-3 c ancel p ointer a djustment s cenario 43 pointer adjustments 43 pointer adjustments added pointer adjustment no pointer adjustments tt 86 or 87 pointer adjustments no pointer adjustments t cancelled pointer adjustment
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 73 telcordia gr-253-core defines an "87-3 cancel" pointer adjustment, as the "87-3 continuous" pointer adjustment pattern, with an additional pointer adjustment cancelled (or not executed), as shown above in figure 53. telcordia gr-253-core mandates that the intrinsic jitter, within the ds3 signal that is de-mapped from a sonet signal, which is experiencing the "87-3 cancel" pattern of pointer adjustments, must not exceed 1.3ui- pp. 9.5.8 continuous pattern figure 54 presents an illustration of the "continuous" pointer adjustment scenario per telcordia gr-253- core. telcordia gr-253-core mandates that the intrinsic jitter, within the ds3 signal that is de-mapped from a sonet signal, which is experiencing the "continuous" pattern of pointer adjustments, must not exceed 1.0ui- pp. the spacing between individual pointer adjustments (within this scenario) can range from 7.5ms to 10s. 9.5.9 continuous add figure 55 presents an illustration of the "continuous add pattern" pointer adjustment scenario per telcordia gr-253-core. f igure 54. i llustration of c ontinuous p eriodic p ointer a djustment s cenario initialization measurement period repeating continuous pattern (see below) pointer adjustment events t
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 74 telcordia gr-253-core defines an "continuous add" pointer adjustment, as the "continuous" pointer adjustment pattern, with an additional pointer adjustment inserted, as shown above in figure 55. telcordia gr-253-core mandates that the intrinsic jitter, within the ds3 signal that is de-mapped from a sonet signal, which is experiencing the "continuous add" pattern of pointer adjustments, must not exceed 1.3ui-pp. 9.5.10 continuous cancel figure 56 presents an illustration of the "continuous cancel pattern" pointer adjustment scenario per telcordia gr-253-core. f igure 55. i llustration of c ontinuous -a dd p ointer a djustment s cenario f igure 56. i llustration of c ontinuous -c ancel p ointer a djustment s cenario continuous pointer adjustments continuous pointer adjustments added pointer adjustment tt continuous pointer adjustments t cancelled pointer adjustment
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 75 telcordia gr-253-core defines a "continuous cancel" pointer adjustment, as the "continuous" pointer adjustment pattern, with an additional pointer adjustment cancelled (or not executed), as shown above in figure 56. telcordia gr-253-core mandates that the intrinsic jitter, within the ds3 signal that is de-mapped from a sonet signal, which is experiencing the "continuous cancel" pattern of pointer adjustments, must not exceed 1.3ui-pp. 9.6 a review of the ds3 wander requirements per ansi t1.105.03b-1997. to be provided in the next revision of this data sheet. 9.7 a review of the intrinsic jitter and wander capabilities of the liu in a typical system application the intrinsic jitter and wander test results are summarized in this section. 9.7.1 intrinsic jitter test results the intrinsic jitter test results for the liu in ds3 being de-mapped from sonet is summarized below in table 2. n otes : 1. a detailed test report on our test procedures and test results is available and can be obtained by contacting your exar sales representative. 2. these test results were obtained via the lius mounted on our xrt94l43 12-channel ds3/e3/sts-1 mapper evaluation board. 3. these same results apply to sdh/au-3 mapping applications. t able 19: s ummary of "c ategory i i ntrinsic j itter t est r esults " for sonet/ds3 a pplications s cenario d escription s cenario n umber liu i ntrinsic j itter t est r esults t elcordia gr-253-core c ategory i i ntrinsic j itter r equirements ds3 de-mapping jitter 0.13ui-pp 0.4ui-pp single pointer adjustment a1 0.201ui-pp 0.43ui-pp (e.g. 0.13ui-pp + 0.3ui-pp) pointer bursts a2 0.582ui-pp 1.3ui-pp phase transients a3 0.526ui-pp 1.2ui-pp 87-3 pattern a4 0.790ui-pp 1.0ui-pp 87-3 add a5 0.926ui-pp 1.3ui-pp 87-3 cancel a5 0.885ui-pp 1.3ui-pp continuous pattern a4 0.497ui-pp 1.0ui-pp continuous add a5 0.598ui-pp 1.3ui-pp continuous cancel a5 0.589ui-pp 1.3ui-pp
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 76 9.7.2 wander measurement test results wander measurement test results will be provided in the next revision of the liu data sheet. 9.8 designing with the liu in this section, we will discuss the following topics. how to design with and configure the liu to permit a system to meet the above-mentioned intrinsic jitter and wander requirements. how is the liu able to meet the above-mentioned requirements? how does the liu permits the user to comply with the sonet aps recovery time requirements of 50ms (per telcordia gr-253-core)? how should one configure the liu, if one needs to support "daisy-chain" testing at the end customer's site? 9.8.1 how to design and configure the liu to permit a system to meet the above-mentioned intrinsic jitter and wander requirements as mentioned earlier, in most application (in which the liu will be used in a sonet de-sync application) the user will typically interface the liu to a mapper device in the manner as presented below in figure 57. in this application, the mapper has the responsibility of receiving a sonet sts-n/oc-n signal and extracting as many as n ds3 signals from this signal. as a given channel within the mapper ic extracts out a given ds3 signal (from sonet) it will typically be applying a clock and data signal to the "transmit input" of the liu ic. figure 57 presents a simple illustration as to how one channel, within the liu should be connected to the mapper ic. as mentioned above, the mapper ic will typically output a clock and data signal to the liu. in many cases, the mapper ic will output the contents of an entire sts-1 data-stream via the data signal to the liu. however, the mapper ic typically only supplies a clock pulse via the clock signal to the liu coincident to whenever a ds3 bit is being output via the data signal. in this case, the mapper ic would not supply a clock edge coincident to when a toh, poh or any non-ds3 data-bit is being output via the data-signal. figure 57 indicates that the data signal from the mapper device should be connected to the tpdata_n input pin of the liu ic and that the clock signal from the mapper device should be connected to the tclk_n input pin of the liu ic. in this application, the liu has the following responsibilities. f igure 57. i llustration of the liu being connected to a m apper ic for sonet d e -s ync a pplications ds3 to sts-n mapper/ demapper ic ds3 to sts-n mapper/ demapper ic liu liu sts-n signal tpdata_n input pin tclk n in p ut de-mapped (gapped) ds3 data and clock
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 77 using a particular clock edge within the "gapped" clock signal (from the mapper ic) to sample and latch the value of each ds3 data-bit that is output from the mapper ic. to (through the user of the jitter attenuator block) attenuate the jitter within this "ds3 data" and "clock signal" that is output from the mapper ic. to convert this "smoothed" ds3 data and clock into industry-compliant ds3 pulses, and to output these pulses onto the line. to configure the liu to operate in the correct mode for this application, the user must execute the following configuration steps. a. configure the liu to operate in the ds3 mode the user can configure a given channel (within the liu) to operate in the ds3 mode, by executing either of the following steps. if the liu has been configured to operate in the host mode the user can accomplish this by setting both bits 2 (e3_n) and bits 1 (sts-1/ds3*_n), within each of the "channel control registers" to "0" as depicted below. if the liu has been configured to operate in the hardware mode the user can accomplish this by pulling all of the following input pins "low". pin 76 - e3_0 pin 94 - e3_1 pin 85 - e3_2 pin 72 - sts-1/ds3 _0 pin 98 - sts-1/ds3 _1 pin 81 - sts-1/ds3 _2 b. configure the liu to operate in the single-rail mode since the mapper ic will typically output a single "data line" and a "clock line" for each ds3 signal that it demaps from the incoming sts-n signal, it is imperative to configure each channel within the liu to operate in the single rail mode. the user can accomplish this by executing either of the following steps. if the liu has been configured to operate in the host mode the user can accomplish this by setting bit 0 (sr/dr*), within the each of the "channel control" registers to 1, as illustrated below. channel control register channel - 0 address location = 0x06, channel - 1 address location = 0x0e, channel - 2 address location = 0x16 b it 7b it 6b it 5b it 4b it 3b it 2b it 1 b it 0 unused prbs enable ch_n rlb_n llb_n e3_n sts-1/ds3 _n sr/dr _n r/o r/o r/w r/w r/w r/w r/w r/w 0000000 0
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 78 if the liu has been configured to operate in the hardware mode then the user should tie the (sr/dr*) pin to "high". c. configure each of the channels within the liu to operate in the sonet de-sync mode the user can accomplish this by executing either of the following steps. if the liu has been configured to operate in the host mode. then the user should set bit d2 (ja0) to "0" and bit d0 (ja1) to "1", within the jitter attenuator control register, as depicted below. if the liu has been configured to operate in the hardware mode then the user should tie pin 44 (ja0) to a logic "high" and pin 42 (ja1) to a logic "low". once the user accomplishes either of these steps, then the jitter attenuator (within the liu) will be configured to operate with a very narrow bandwidth. d. configure the jitter attenuator (within each of the channels) to operate in the transmit direction. the user can accomplish this by executing either the following steps. if the liu has been configured to operate in the host mode. then the user should be bit d1 (jatx/jarx*) to "1", within the jitter attenuator control register, as depicted below. channel control register channel 0 address location = 0x06, channel 1 address location = 0x0e, channel 2 address location = 0x16 b it 7b it 6b it 5b it 4b it 3b it 2b it 1 b it 0 unused prbs enable ch_n rlb_n llb_n e3_n sts-1/ ds3 _n sr/dr _n r/o r/o r/w r/w r/w r/w r/w r/w 0000000 1 jitter attenuator control register channel 0 address location = 0x07, channel 1 address location = 0x0f, channel 2 address location = 0x17 b it 7b it 6b it 5b it 4b it 3 b it 2b it 1 b it 0 unused sonet aps recovery time disablech_n ja reset ch_n ja1 ch_n ja in tx path ch_n ja0 ch_n r/o r/o r/o r/w r/w r/w r/w r/w 00000 00 1
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 79 if the liu has been configured to operate in the hardware mode. then the user should tie pin 43 (jatx/jarx*) to "1". e. enable the sonet aps recovery time" mode finally, if the user intends to use the liu in an application that is required to reacquire proper sonet and ds3 traffic, prior within 50ms of an aps (automatic protection switching) event (per telcordia gr-253-core), then the user should set bit 4 (sonet aps recovery time disable), within the "jitter attenuator control" register, to "0" as depicted below. n otes : 1. the ability to disable the "sonet aps recovery time" mode is only available if the liu is operating in the host mode. if the liu is operating in the "hardware" mode, then this "sonet aps recovery time mode" feature will always be enabled. 2. the "sonet aps recovery time" mode will be discussed in greater detail in section 9.8.3, how does the liu permit the user to comply with the sonet aps recovery time requirements of 50ms (per telcordia gr-253- core)? on page 83. 9.8.2 recommendations on pre-processing the gapped clocks (from the mapper/asic device) prior to routing this ds3 clock and data-signals to the transmit inputs of the liu in order to minimize the effects of "clock-gapping" jitter within the ds3 signal that is ultimately transmitted to the ds3 line (or facility), we recommend that some "pre-processing" of the "data-signals" and "clock-signals" (which are output from the mapper device) be implemented prior to routing these signals to the "transmit inputs" of the liu. 9.8.2.1 some notes prior to starting this discussion: our simulation results indicate that jitter attenuator pll (within the liu liu ic) will have no problem handling and processing the "data-signal" and "clock-signal" from a mapper ic/asic if no pre-processing has been performed on these signals. in order words, our simulation results indicate that the jitter attenuator pll (within the liu ic) will have no problem handling the "worst-case" of 59 consecutive bits of no clock pulses in the "clock-signal (due to the mapper ic processing the toh bytes, an incrementing pointer-adjustment- jitter attenuator control register channel 0 address location = 0x07, channel 1 address location = 0x0f, channel 2 address location = 0x17 b it 7b it 6b it 5b it 4b it 3b it 2 b it 1b it 0 unused sonet aps recovery time disablech_n ja reset ch_n ja1 ch_n ja in tx path ch_n ja0 ch_n r/o r/o r/o r/w r/w r/w r/w r/w 000000 11 jitter attenuator control register channel 0 address location = 0x07, channel 1 address location = 0x0f, channel 2 address location = 0x17 b it 7b it 6b it 5 b it 4b it 3b it 2b it 1b it 0 unused sonet aps recovery time disablech_n ja reset ch_n ja1 ch_n ja in tx path ch_n ja0 ch_n r/o r/o r/o r/wr/wr/wr/wr/w 000 00001
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 80 induced "stuffed-byte", the poh byte, and the two fixed-stuff bytes within the sts-1 spe, etc), immediately followed be processing clusters of ds3 data-bits (as shown in figure 37) and still comply with the "category i intrinsic jitter requirements per telcordia gr-253-core for ds3 applications. n ote : if this sort of "pre-processing" is already supported by the mapper device that you are using, then no further action is required by the user. 9.8.2.2 our pre-processing recommendations for the time-being, we recommend that the customer implement the "pre-processing" of the ds3 "data-signal" and "clock-signal" as described below. currently we are aware that some of the mapper products on the market do implement this exact "pre-processing" algorithm. however, if the customer is implementing their mapper design in an asic or fpga solution, then we strongly recommend that the user implement the necessary logic design to realize the following recommendations. some time ago, we spent some time, studying (and then later testing our solution with) the pm5342 oc-3 to ds3 mapper ic from pmc-sierra. in particular, we wanted to understand the type of "ds3 clock" and "data" signal that this ds3 to oc-3 mapper ic outputs. during this effort, we learned the following. 1. this "ds3 clock" and "data" signal, which is output from the mapper ic consists of two major "repeating" patterns (which we will refer to as "major pattern a" and "major pattern b". the behavior of each of these patterns is presented below. major pattern a major pattern a consists of two "sub" or minor-patterns, (which we will refer to as "minor pattern p1 and p2). minor pattern p1 consists of a string of seven (7) clock pulses, followed by a single gap (no clock pulse). an illustration of minor pattern p1 is presented below in figure 58. it should be noted that each of these clock pulses has a period of approximately 19.3ns (or has an "instantaneously frequency of 51.84mhz). minor pattern p2 consists of string of five (5) clock pulses, which is also followed by a single gap (no clock pulse). an illustration of pattern p2 is presented below in figure 59. f igure 58. i llustration of minor pattern p1 1 2 3 4 5 6 7 missing clock pulse
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 81 how major pattern a is synthesized major pattern a is created (by the mapper ic) by: repeating minor pattern p1 (e.g., 7 clock pulses, followed by a gap) 63 times. upon completion of the 63rd transmission of minor pattern p1, minor pattern p2 is transmitted repeatedly 36 times. figure 60 presents an illustration which depicts the procedure that is used to synthesize major pattern a hence, major pattern a consists of "(63 x 7) + (36 x 5)" = 621 clock pulses. these 621 clock pulses were delivered over a period of "(63 x 8) + (36 x 6)" = 720 sts-1 (or 51.84mhz) clock periods. major pattern b major pattern b consists of three sub or minor-patterns (which we will refer to as "minor patterns p1, p2 and p3). minor pattern p1, which is used to partially synthesize major pattern b, is exactly the same "minor pattern p1" as was presented above in figure 30. similarly, the minor pattern p2, which is also used to partially synthesize major pattern b, is exactly the same "minor pattern p2" as was presented in figure 31. minor pattern p3 (which has yet to be defined) consists of a string of six (6) clock pulses, which contains no gaps. an illustration of minor pattern p3 is presented below in figure 61. f igure 59. i llustration of minor pattern p2 f igure 60. i llustration of p rocedure which is used to s ynthesize major pattern a 1 2 3 4 5 missing clock pulse minor pattern p1 minor pattern p2 repeats 63 times repeats 36 times
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 82 how major pattern b is synthesized major pattern b is created (by the mapper ic) by: repeating minor pattern p1 (e.g., 7 clock pulses, followed by a gap) 63 times. upon completion of the 63rd transmission of minor pattern p1, minor pattern p2 is transmitted repeatedly 36 times. pon completion of the 35th transmission of minor pattern p2, minor pattern p3 is transmitted once. figure 62 presents an illustration which depicts the procedure that is used to synthesize major pattern b. hence, major pattern b consists of "(63 x 7) + (35 x 5)" + 6 = 622 clock pulses. these 622 clock pulses were delivered over a period of "(63 x 8) + (35 x 6) + 6 = 720 sts-1 (or 51.84mhz) clock periods. putting the patterns together finally, the ds3 to oc-n mapper ic clock output is reproduced by doing the following. major pattern a is transmitted two times (repeatedly). after the second transmission of major pattern a, major pattern b is transmitted once. then the whole process repeats. throughout the remainder of this document, we will refer to this particular pattern as the "super pattern". figure 63 presents an illustration of this "super pattern" which is output via the mapper ic. f igure 61. i llustration of minor pattern p3 f igure 62. i llustration of p rocedure which is used to s ynthesize pattern b 1 2 3 4 5 6 pattern p1 pattern p2 repeats 63 times repeats 35 times pattern p3 transmitted 1 time
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 83 cross-checking our data each super pattern consists of (621 + 621 + 622) = 1864 clock pulses. the total amount of time, which is required for the "ds3 to oc-n mapper" ic to transmit this super pattern is (720 + 720 + 720) = 2160 "sts-1" clock periods. this amount to a period of (2160/51.84mhz) = 41,667ns. in a period of 41, 667ns, the liu (when configured to operate in the ds3 mode), will output a total (41,667ns x 44,736,000) = 1864 uniformly spaced ds3 clock pulses. hence, the number of clock pulses match. applying the super pattern to the liu whenever the liu is configured to operate in a "sonet de-sync" application, the device will accept a continuous string of the above-defined super pattern, via the tclk input pin (along with the corresponding data). the channel within the liu (which will be configured to operate in the "ds3" mode) will output a ds3 line signal (to the ds3 facility) that complies with the "category i intrinsic jitter requirements - per telcordia gr-253-core (for ds3 applications). this scheme is illustrated below in figure 64. 9.8.3 how does the liu permit the user to comply with the sonet aps recovery time requirements of 50ms (per telcordia gr-253-core)? telcordia gr-253-core, section 5.3.3.3 mandates that the "aps completion" (or recovery) time be 50ms or less. many of our customers interpret this particular requirement as follows. "from the instant that an aps is initiated on a high-speed sonet signal, all lower-speed sonet traffic (which is being transported via this "high-speed" sonet signal) must be fully restored within 50ms. similarly, if the "high-speed" sonet signal is transporting some pdh signals (such as ds1 or ds3, etc.), then those entities f igure 63. i llustration of the super pattern which is output via the "oc-n to ds3" m apper ic f igure 64. s imple i llustration of the liu being used in a sonet d e -s ynchronizer " a pplication pattern a pattern a pattern b ds3 to sts-n mapper/ demapper ic ds3 to sts-n mapper/ demapper ic liu liu sts-n signal tpdata_n input pin tclk_n input de-mapped (gapped) ds3 data and clock
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 84 that are responsible for acquiring and maintaining ds1 or ds3 frame synchronization (with these ds1 or ds3 data-streams that have been de-mapped from sonet) must have re-acquired ds1 or ds3 frame synchronization within 50ms" after aps has been initiated." the liu was designed such that the ds3 signals that it receives from a sonet mapper device and processes will comply with the category i intrinsic jitter requirements per telcordia gr-253-core. reference 1 documents some aps recovery time testing, which was performed to verify that the jitter attenuator blocks (within the liu) device that permit it to comply with the category i intrinsic jitter requirements (for ds3 applications) per telcordia gr-253-core, do not cause it to fail to comply with the "aps completion time" requirements per section 5.3.3.3 of telcordia gr-253-core. however, table 20 presents a summary of some aps recovery time requirements that were documented within this test report. n ote : the aps completion (or recovery) time requirement is 50ms. configuring the liu to be able to comply with the sonet aps recovery time requirements of 50ms quite simply, the user can configure a given jitter attenuator block (associated with a given channel) to (1) comply with the "aps completion time" requirements per telcordia gr-253-core, and (2) also comply with the "category i intrinsic jitter requirements per telcordia gr-253-core (for ds3 applications) by making sure that bit 4 (sonet aps recovery time disable ch_n), within the jitter attenuator control register is set to "0" as depicted below. t able 20: m easured aps r ecovery t ime as a function of ds3 ppm offset ds3 ppm o ffset ( per w&g ant-20se) m easured aps r ecovery t ime ( per l ogic a nalyzer ) -99 ppm 1.25ms -40ppm 1.54ms -30 ppm 1.34ms -20 ppm 1.49ms -10 ppm 1.30ms 0 ppm 1.89ms +10 ppm 1.21ms +20 ppm 1.64ms +30 ppm 1.32ms +40 ppm 1.25ms +99 ppm 1.35ms jitter attenuator control register channel 0 address location = 0x07, channel 1 address location = 0x0f, channel 2 address location = 0x17 b it 7b it 6b it 5 b it 4b it 3b it 2b it 1b it 0 unused sonet aps recovery time disable ch_n ja reset ch_n ja1 ch_n ja in tx path ch_n ja0 ch_n r/o r/o r/o r/wr/wr/wr/wr/w 000 00011
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 85 n ote : the user can only disable the "sonet aps recovery time mode" if the liu is operating in the host mode. if the user is operating the liu in the hardware mode, then the user will have no ability to disable the "sonet aps recovery time mode" feature. 9.8.4 how should one configure the liu, if one needs to support "daisy-chain" testing at the end customer's site? daisy-chain testing is emerging as a new requirements that many of our customers are imposing on our sonet mapper and liu products. many system designer/manufacturers are finding out that whenever their end-customers that are evaluating and testing out their systems (in order to determine if they wish to move forward and start purchasing this equipment in volume) are routinely demanding that they be able to test out these systems with a single piece of test equipment. this means that the end-customer would like to take a single piece of ds3 or sts-1 test equipment and (with this test equipment) snake the ds3 or sts-1 traffic (that this test equipment will generate) through many or (preferably all) channels within the system. for example, we have had request from our customers that (on a system that supports oc-192) our silicon be able to support this ds3 or sts-1 traffic snaking through the 192 ds3 or sts-1 ports within this system. after extensive testing, we have determined that the best approach to complying with test "daisy-chain" testing requirements, is to configure the jitter attenuator blocks (within each of the channels within the liu) into the "32-bit" mode. the user can configure the jitter attenuator block (within a given channel of the liu) to operate in this mode by settings in the table below. references 1. test report - automatic protection switching (aps) recovery time testing with the xrt94l43 ds3/e3/sts-1 to sts-12 mapper ic - revision c silicon jitter attenuator control register channel 0 address location = 0x07, channel 1 address location = 0x0f, channel 2 address location = 0x17 b it 7b it 6b it 5b it 4b it 3 b it 2b it 1 b it 0 unused sonet aps recovery time disable ch_n ja reset ch_n ja1 ch_n ja in tx path ch_n ja0 ch_n r/o r/o r/o r/w r/w r/w r/w r/w 00000 11 0
XRT75L00D rev. 1.0.2 e3/ds3/sts-1 line interface unit with sonet desynchronizer 86 ordering information package dimensions p art n o .p ackage o perating t emperature r ange XRT75L00Div 52 pin tqfp (10mm x 10mm) -40c to +85c symbol min max min max a 0.055 0.063 1.40 1.60 a1 0.002 0.006 0.05 0.15 a2 0.053 0.057 1.35 1.45 b 0.009 0.015 0.22 0.38 c 0.004 0.008 0.09 0.20 d 0.465 0.480 11.80 12.20 d1 0.390 0.398 9.90 10.10 e 0.0256 bsc 0.65 bsc l 0.018 0.030 0.45 0.75 a 0 7 0 7 b aaa - 0.003 - 0.08 7 typ 7 typ inches millimeters note: the control dimension is the millimeter column 39 27 26 14 113 40 52 d d 1 d d 1 b e a a 2 a 1 a seating plane l c
XRT75L00D e3/ds3/sts-1 line interface unit with sonet desynchronizer rev. 1.0.2 87 notice exar corporation reserves the right to make changes to the products contained in this publication in order to improve design, performance or reliability. exar corporation assumes no responsibility for the use of any circuits described herein, conveys no license under any patent or other right, and makes no representation that the circuits are free of patent infringement. charts and schedules contained here in are only for illustration purposes and may vary depending upon a users specific application. while the information in this publication has been carefully checked; no responsibility, however, is assumed for inaccuracies. exar corporation does not recommend the use of any of its products in life support applications where the failure or malfunction of the product can reasonably be expected to cause failure of the life support system or to significantly affect its safety or effectiveness. products are not authorized for use in such applications unless exar corporation receives, in writing, assurances to its satisfaction that: (a) the risk of injury or damage has been minimized; (b) the user assumes all such risks; (c) potential liability of exar corporation is adequately protected under the circumstances. copyright 2004 exar corporation datasheet february 2004. reproduction, in part or whole, without the prior written consent of exar corporation is prohibited. revision history 1.0.1 added a detailed section on the de-sync feature. removed evaluation schematic. 1.0.2 incorrect pin number references in de-sync functional description. added 128-bit fifo information for the de-sync function. changed the device id to reflect the correct value.

▲Up To Search▲

Price & Availability of XRT75L00D

	To Download XRT75L00D Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .